- kick an uma rarity is not fully documented in the available public guide.
- Confirmed units include Curren Chan and Mejiro Palmer from listed code rewards.
- Do not rank units by code availability, reward timing, or character popularity.
- Check official channels before trusting community rarity charts or pull claims.
- Track evidence by recording each unit, source, banner, and stated rarity.
What kick an uma rarity Currently Confirms
The phrase kick an uma rarity usually refers to how Uma characters are classified, compared, or obtained in the Roblox experience. The available September 2026 guide confirms that the game features collectible Uma units and that some codes can provide specific characters, but it does not publish a verified rarity table.
That distinction matters. A unit appearing as a code reward does not automatically make it common, rare, legendary, or stronger than another unit. Likewise, a character being available through an event or group reward does not establish a permanent rarity tier. Until the game displays official rarity labels, players should separate confirmed facts from community speculation.
| Confirmed detail | What it tells players | What it does not prove |
|---|---|---|
Curren Chan is listed as a reward for 300KVISITS | The character can be associated with that published code reward | It does not prove Curren Chan's rarity or combat value |
Mejiro Palmer is listed as a reward for 30KGROUP | The character is connected with a group milestone reward | It does not prove the unit is a basic, rare, or premium Uma |
1000CARATS grants 1,000 carats | Carats are a listed currency reward | It does not reveal the odds or value of any unit |
| Codes are entered through the top-left codes button | Players have a direct redemption route | It does not confirm a banner or summon rarity system |
| New units may be announced through the official community server | The community channel can be useful for updates | An announcement alone does not establish a formal tier |
No reliable source in the current reference material confirms S, A, B, Mythic, Legendary, or similar rarity tiers for Kick an Uma. Treat charts using those labels as unverified unless the game itself or its creators publish them.
The most dependable starting point is the published Kick an Uma code guide, which identifies the listed unit rewards and redemption process. Use it as a reference for code-related information, not as proof of a complete rarity ranking.
How to Evaluate Uma Unit Rarity
A useful rarity guide needs more than a character name. Players should look for several signals that can be checked in-game or through an official announcement. These signals help distinguish a real rarity classification from assumptions based on design, popularity, or availability.
Official Label
A rarity name or color shown directly in the unit menu, banner, index, or reward screen is the strongest evidence.
Acquisition Method
Banner, event, code, quest, and shop availability can provide context, but availability alone does not define rarity.
Update Evidence
Patch notes, creator announcements, and official community posts can confirm when a unit or tier changes.
| Evidence type | Reliability | How to use it |
|---|---|---|
| In-game rarity label | High | Record the exact label and where it appears |
| Official creator announcement | High | Check whether the post names a tier, banner, or drop rate |
| Unit index color or icon | Medium | Use only if the interface explains what the color means |
| Banner placement | Medium | Treat as context unless the banner lists rarity rules |
| Code reward status | Low for rarity | Confirm the reward, but do not assign a tier |
| Community ranking | Variable | Use for opinions, not as verified game data |
| Character popularity | Low | Popularity is not a rarity classification |
The current code information is especially useful for understanding this limitation. Curren Chan and Mejiro Palmer are named as rewards, while the carat code provides currency. Nothing in that listing states that either character has a particular tier. A careful wiki should preserve that uncertainty rather than fill the gap with invented rankings.
When you find a new Uma, capture the unit name, acquisition method, displayed label, announcement date, and source link. This creates a useful record without guessing missing statistics.
Step-by-Step Rarity Tracking Method
Use the following process whenever a new character, code, banner, or event appears. It is designed to keep a personal rarity list accurate while the game’s public documentation develops.
Record the Exact Unit Name
Write the character name exactly as displayed. Avoid combining alternate versions, event variants, or similarly named units into one entry.
Identify the Acquisition Route
Note whether the unit comes from a code, banner, event, quest, shop, group milestone, or another method. This describes availability but does not automatically determine rarity.
Check the In-Game Label
Look at the unit menu, collection index, reward screen, or summon interface for an explicit rarity name, color key, star count, or drop-rate explanation.
Compare Official Announcements
Search the creator’s Roblox page, official Discord, or other official community channel for a matching announcement. Confirm that the announcement refers to the same unit version.
Mark Unknown Details Clearly
If no official label is available, write “rarity not confirmed.” Do not replace missing evidence with a community tier or a personal power rating.
| Tracking field | Example entry | Why it matters |
|---|---|---|
| Unit | Curren Chan | Keeps the record tied to a named character |
| Source | 300KVISITS code listing | Shows how the unit was documented |
| Acquisition type | Code reward | Describes access without assigning rarity |
| Official tier | Not stated | Prevents unsupported ranking claims |
| Date checked | September 11, 2026 | Shows when the information was reviewed |
This method also helps when information changes. A code may expire, an event may end, or a unit may later receive a visible tier label. Keeping the original acquisition record separate from the later update prevents old information from being mistaken for current rarity data.
A clearly marked “unknown” entry is more useful than an invented tier. Update it only when an official screen or creator statement supplies new evidence.
Rarity, Availability, and Strength Are Different
Players often use rarity as shorthand for overall value, but these concepts should remain separate. A character may be difficult to obtain without being the strongest unit, while a code-reward character may be easy to claim without being a low-tier option.
| Category | Meaning | Safe conclusion |
|---|---|---|
| Rarity | How the game classifies or distributes a unit | Requires an official label or stated rule |
| Availability | How players currently obtain the unit | Can change when codes or events expire |
| Strength | Performance in the game’s actual mechanics | Requires tested stats, abilities, and use cases |
| Popularity | How often players discuss or select a unit | Does not establish rarity or performance |
| Value | Practical benefit compared with effort or cost | Depends on player goals and available resources |
For example, the listed code rewards show that Curren Chan and Mejiro Palmer have documented access routes in the referenced guide. That makes them useful entries for an availability record. It does not tell players whether they outperform other Umas, whether they have a higher drop chance, or whether they belong to a premium tier.
A strong wiki entry should therefore use precise wording:
- “Listed as a code reward” is supported.
- “Available through a group-related code” is supported for the named reward.
- “Limited-time” should only be used when an expiration or event window is confirmed.
- “Rare,” “secret,” “best,” or “meta” requires additional evidence.
- “High damage” or “top unit” requires verified mechanics or testing.
Describe what a source proves, then stop there. Separating rarity, access, and strength keeps your guide useful even when the game adds new units or changes its systems.
Current Unit Evidence Table
| Unit or reward | Documented status | Rarity status | Recommended wiki wording |
|---|---|---|---|
| Curren Chan | Listed as a reward for 300KVISITS | Not confirmed | “Curren Chan is listed as a code reward” |
| Mejiro Palmer | Listed as a reward for 30KGROUP | Not confirmed | “Mejiro Palmer is listed as a group-related code reward” |
| 1,000 carats | Currency reward for 1000CARATS | Not applicable | “The code lists a carat reward, not a unit rarity” |
SORRY4DELAY | Listed among expired codes | Not applicable | “The code is reported as expired in the referenced guide” |
Rarity Checklist and FAQ
Use this checklist before adding a unit to a Kick an Uma rarity article, tier list, or collection page.
Rarity Verification Checklist:
- Confirm the exact Uma name and variant
- Record the acquisition method and source date
- Look for an official in-game rarity label
- Check creator announcements or official community posts
- Separate rarity from strength, popularity, and availability
Practical Comparison Guide
| Claim | Evidence needed | Status with current reference |
|---|---|---|
| A unit is obtainable | Reliable reward or acquisition listing | Supported for the named code rewards |
| A unit is rare | Official rarity label or stated distribution rule | Not confirmed |
| A unit is the strongest | Verified stats, abilities, or testing | Not confirmed |
| A code is active | Current redemption confirmation | Must be checked before use |
| A code has expired | A current guide or official expiration notice | Reported for SORRY4DELAY in the referenced guide |
Q: What does kick an uma rarity mean?
It refers to the classification or perceived scarcity of Uma characters in the Roblox experience. The available reference confirms named code rewards but does not provide a verified rarity tier list.
Q: Are Curren Chan and Mejiro Palmer confirmed rare units?
No. They are confirmed as named rewards in the referenced code guide, but that information does not assign either unit a rarity tier.
Q: Can a code reward prove that a unit is common or limited?
No. A code shows an acquisition route. It does not, by itself, prove a unit's rarity, drop rate, strength, or long-term availability.
Q: Where should players check for future rarity updates?
Check the in-game unit interface first, then review the creator's Roblox page and official community channels. Record the date and exact wording of any new rarity announcement.
The safest approach for September 2026 is to maintain a verified evidence list instead of publishing unsupported rankings. As new menus, banners, events, or creator announcements appear, update each unit individually and preserve the distinction between confirmed information and community interpretation.
Do not label any Uma as S-tier, legendary, mythic, or limited unless the game or its creators provide evidence for that classification. Recheck code status and unit details before presenting them as current.