All Umamusume Characters’ Ages and Birthdays

If you’ve ever tried to pin down an Umamusume character’s exact age and felt like you were fighting RNG with no pity system, that confusion is intentional. The franchise treats age less like a hard stat and more like a hidden value behind the UI. Birthdays are public, celebrated, and mechanically acknowledged, but chronological age is a different beast entirely.

This design choice isn’t a lore accident or localization gap. It’s a deliberate framework tied to the Tracen Academy setting, the game’s seasonal structure, and the way Cygames wants characters to remain evergreen across years of updates, banners, and anime adaptations.

The Tracen Academy School System

Every playable Umamusume is enrolled at Tracen Academy, which functions more like an elite sports academy than a standard Japanese school. Students are grouped by year, such as junior-classmen and senior-classmen, but those labels rarely map cleanly to real-world ages. Think of it like ranked tiers rather than a birth-year-based progression.

Canon material avoids assigning numerical ages to almost all characters, even in profiles that list height, weight, and measurements with surgical precision. The only consistent rule is that they are considered students, which places them broadly in a late-teen range without locking anyone to a specific number. This lets characters like Symboli Rudolf and Tokai Teio exist in the same “school” while clearly projecting vastly different levels of experience and presence.

Seasons, Years, and the Floating Timeline

Umamusume operates on a floating timeline where seasons pass, races cycle, and birthdays occur, but characters do not visibly age out of the academy. Your Trainer can celebrate the same Uma’s birthday multiple in-game years in a row with zero stat decay or narrative consequences. From a systems perspective, age never ticks upward like a cooldown timer.

This seasonal loop is crucial for live-service longevity. New players can start in 2026 and still meet Special Week at the same stage of her career as someone who started at launch. Anime seasons, manga arcs, and event stories all plug into this elastic timeline without breaking canon, even when they reference different race years or historical counterparts.

Confirmed Birthdays vs. Unspecified Ages

Here’s where things get deceptively precise. Every Umamusume has an officially confirmed birthday sourced from in-game profiles, guidebooks, and Japanese promotional material. These dates are canon, celebrated in-game, and often tied to real-life racehorse birthdates.

Ages, however, are almost never confirmed numerically. When a character feels “older” or “younger,” that impression comes from writing, voice direction, and narrative role, not hard data. Any exact age you see online is either inferred, speculative, or pulled from non-canon parallels, which is why this article separates confirmed facts from fandom math.

Why Canon Ambiguity Is Intentional

From a design standpoint, locking ages would create unnecessary constraints on future content. Character growth in Umamusume is mechanical and emotional, not chronological. You’re leveling skills, optimizing race strategies, and refining builds, not watching characters age out like expired units.

Lore-wise, this ambiguity keeps the focus on legacy rather than lifespan. Umamusume is about inheriting dreams, records, and rivalries across generations, not tracking birthdays like a spreadsheet. Understanding this framework is key before diving into individual character data, because it explains why birthdays are absolute, ages are fluid, and both coexist without contradiction.

How Birthdays Work in Umamusume: In-Game Profiles, Official Sources, and Anniversary Events

With the age question deliberately left elastic, birthdays become the one hard anchor in Umamusume’s character data. They’re not flavor text or optional trivia; they’re canonized identifiers baked directly into the game’s UI, event cadence, and marketing cycle. Understanding how birthdays function explains why players can talk about precise dates with confidence, while still treating ages as intentionally fluid.

In-Game Profiles: Where Birthdays Are Locked In

Every playable Umamusume has a birthday listed in her in-game profile, viewable from the character menu. These dates are fixed, unchanging, and consistent across all regions of the game. If a character launches with a birthday on, say, April 14, that date will still be April 14 years later, regardless of how many training cycles you’ve cleared.

Crucially, these birthdays are treated as canonical data, not seasonal placeholders. They’re referenced in dialogue, acknowledged by support cards, and sometimes directly commented on by other characters. From a systems perspective, birthdays function more like permanent character metadata than narrative milestones.

Official Sources: Japanese Guidebooks, Developer Material, and Horse Lineage

Outside the game client, birthdays are reinforced through Japanese-only guidebooks, official websites, and promotional material released by Cygames. In most cases, an Umamusume’s birthday directly matches the real-world birthdate of her racehorse counterpart. This one-to-one mapping is deliberate and consistent across the roster.

What you will not find in these sources is a numerical age. Even when profiles describe a character as a “senior” presence or a “rookie,” the language stays qualitative. This keeps the canon clean: birthdays are factual, ages are interpretive, and neither contradicts the school setting or long-term live-service plans.

Anniversary Events and Birthday Celebrations In-Game

When an Umamusume’s birthday arrives, the game acknowledges it with login bonuses, special dialogue, and occasionally limited-time flavor interactions. These celebrations recur every real-world year, even if you’re technically on your tenth in-game training loop with the same character.

There’s no stat scaling, no aging debuff, and no narrative flag that says “another year has passed.” Think of birthday events as cosmetic buffs to immersion, not progression triggers. They reinforce character attachment without forcing the timeline forward, similar to seasonal events in other live-service RPGs.

Why Birthdays Stay Canon While Ages Stay Unspecified

From a lore and systems standpoint, this split is intentional. Birthdays tie characters to real-world history, horse racing legacy, and annual community engagement. Ages, if locked in, would introduce mechanical and narrative problems, especially in a school-based setting designed to loop endlessly.

The result is a clean hierarchy of information. Birthdays are absolute and verifiable across all official sources. Age status falls into two categories only: officially unspecified or implied through narrative tone, never confirmed numerically. Once you internalize that rule, the entire character roster becomes much easier to read without falling into fandom speculation traps.

Characters with Officially Confirmed Birthdays and Ages

With the framework established, this is where the hard data lives. These characters have birthdays explicitly confirmed by Cygames across in-game profiles, official websites, guidebooks, and promotional material. What varies is age transparency: while birthdays are locked, numerical ages remain deliberately undefined, even for the most lore-heavy Umamusume.

Special Week

Birthday: May 2
Age: Officially unspecified

Special Week’s profile is the cleanest example of Umamusume canon rules in action. Her birthday directly mirrors her real-world racehorse, and every birthday event reinforces that date without advancing her age. Narratively, she’s framed as a first-year trainee early on, but no number is ever assigned, keeping her progression flexible across seasons and story arcs.

Silence Suzuka

Birthday: May 1
Age: Officially unspecified

Suzuka’s birthday is one of the most consistently referenced in promotional campaigns and anniversary art. Despite her veteran aura and mentor-like presence in multiple story routes, the canon never labels her with a numerical age. The contrast between her calm, late-game racer energy and undefined age is intentional, preserving her role across timelines.

Tokai Teio

Birthday: April 20
Age: Officially unspecified

Tokai Teio’s birthday is firmly established and frequently celebrated in-game with unique dialogue. Story chapters describe her as a prodigy with fluctuating form, but never attach an age value to that growth. Her school year placement does the narrative work that an age number would normally handle.

Mejiro McQueen

Birthday: April 3
Age: Officially unspecified

McQueen’s aristocratic demeanor and lineage-heavy writing often make her feel older than her peers. Canon sources resist confirming that assumption. Her birthday is fixed, but her age remains fluid, allowing her to exist comfortably as both a refined senior presence and an active student within the academy loop.

Symboli Rudolf

Birthday: March 13
Age: Officially unspecified

Rudolf comes closest to feeling “aged up” due to her leadership role and authoritative tone. Even so, official materials stop short of assigning her a number. She’s positioned as an upperclassman through narrative authority rather than age mechanics, reinforcing the franchise-wide rule that hierarchy does not equal chronology.

Oguri Cap

Birthday: March 27
Age: Officially unspecified

Oguri Cap’s stoic personality and late-blooming rise could easily justify a confirmed age in another franchise. Umamusume deliberately avoids that path. Her birthday is immutable, but her age exists only as a narrative implication tied to experience, not time passed.

Gold Ship

Birthday: March 6
Age: Officially unspecified

Gold Ship’s chaotic behavior makes age almost irrelevant, and the canon leans into that. While her birthday is officially documented and celebrated annually, no source attempts to quantify her age. This keeps her unpredictable energy evergreen, immune to timeline fatigue.

Why No Character Has a Confirmed Numerical Age

Across the entire playable roster, there are zero Umamusume with a canon numerical age attached to their profile. This isn’t an omission or localization gap; it’s a structural rule. Birthdays anchor characters to real-world racing history, while age remains an intentionally untracked stat, avoiding contradictions with looping training runs, seasonal events, and long-term live-service storytelling.

In practice, every character in this section shares the same age status: officially unspecified by design. That consistency is what keeps the school setting functional, the lore clean, and the roster expandable without retroactive continuity issues.

Characters with Confirmed Birthdays but Unspecified or Flexible Ages

If you’ve played Umamusume for more than a single training cycle, you’ve already felt this design choice in action. Characters celebrate birthdays every year, get special dialogue, limited-time voicelines, and even commemorative campaigns. Yet when it comes to a hard numerical age, the stat simply does not exist in canon.

This isn’t a contradiction. It’s a deliberate systems-level decision that keeps the roster stable across endless seasons, events, and reruns.

How Birthdays Are Locked In Canon

Every Umamusume has a confirmed birthday pulled directly from their real-world racehorse counterpart. This information is treated as immutable canon, referenced consistently across the game, anime adaptations, and official character profiles. Birthdays function like a fixed data flag, similar to base stats or unique skills, and they never change between timelines or story modes.

From Special Week’s May 2 to Tokai Teio’s April 20, these dates are non-negotiable. They anchor each character to racing history while still allowing the game’s narrative to loop freely.

Why Ages Stay Intentionally Unspecified

Aging is where Umamusume draws a hard line. Assigning numerical ages would immediately clash with the academy setting, where characters can be trained, retired, and retrained indefinitely. The moment a character “ages out,” the live-service model breaks, and the illusion of an evergreen roster collapses.

By keeping ages flexible, the game avoids timeline power creep. No one becomes too old to race, no one outlevels the school, and no event has to account for years passing in-universe.

Perceived Age vs. Canon Age

Players often infer age based on personality, voice direction, or narrative role. Characters like Mejiro McQueen feel refined and mature, while others like Nice Nature or Twin Turbo read as younger and more impulsive. These are tonal cues, not lore confirmations.

Canon never validates these assumptions. Regardless of how “aged” a character feels, their official age status remains unspecified, preserving consistency across all modes and adaptations.

Examples Across the Roster

Special Week
Birthday: May 2
Age: Officially unspecified

Tokai Teio
Birthday: April 20
Age: Officially unspecified

Mejiro McQueen
Birthday: April 3
Age: Officially unspecified

Silence Suzuka
Birthday: May 1
Age: Officially unspecified

Daiwa Scarlet
Birthday: April 13
Age: Officially unspecified

These examples aren’t exceptions; they’re the rule. Every playable and story-relevant Umamusume follows this exact structure, with a confirmed birthday and an intentionally untracked age.

How the School Setting Enforces This Rule

The Tracen Academy framework only works if time is elastic. Training arcs reset, seasonal events repeat, and characters can interact endlessly without narrative decay. Fixed ages would introduce continuity debt that no amount of hand-waving could patch over.

By divorcing age from progression, Umamusume treats growth as a gameplay loop rather than a timeline. Characters evolve through skills, stats, and story beats, not birthdays passed.

What This Means for Lore-Focused Players

For players who care about canon accuracy, the takeaway is simple. Birthdays are hard lore, sourced from real racing history and consistently enforced. Ages are soft lore, deliberately left blank to protect the game’s structure.

Any discussion of “how old” a character is remains interpretive, not official. If it’s not stated directly in profile materials, it doesn’t exist in canon, and that’s exactly how Umamusume wants it.

Why Most Umamusume Ages Are Intentionally Undefined: Lore, Narrative Design, and Developer Intent

Coming off the hard line between confirmed birthdays and deliberately blank ages, the design intent becomes clear. This isn’t missing data or an unfinished lore document. It’s a structural choice baked into Umamusume from day one.

Cygames isn’t avoiding the question of age by accident. They’re doing it to keep the entire ecosystem playable, expandable, and canon-safe across years of live service updates.

Narrative Elasticity Is Mandatory for a Live-Service Game

Umamusume operates on looping time, not linear progression. Training arcs restart, events recur annually, and story chapters can be experienced in any order without breaking continuity.

If characters had fixed ages, every rerun would introduce narrative drift. A character celebrating the same birthday event for the third year would either need to age up or exist in a timeline paradox, and neither works in a gacha framework.

By leaving ages undefined, Cygames gives the story infinite I-frames against continuity damage. The lore never takes a hit, no matter how long the game runs.

The Tracen Academy Setting Is a Controlled Sandbox

Tracen Academy isn’t a real-world school with grades, graduation years, or age brackets. It’s a narrative container designed to justify training, competition, and character interaction indefinitely.

Students don’t age out, don’t graduate on-screen, and don’t move into adult racing circuits. That’s not an oversight; it’s a rule. Age would introduce an endpoint, and Umamusume is built to avoid hard endpoints at all costs.

In gameplay terms, Tracen is a perfectly balanced map with no forced exits. Age would be an invisible wall the developers intentionally removed.

Cross-Media Canon Demands Age Ambiguity

The Umamusume anime, manga adaptations, stage plays, and the game all share a unified canon. Characters must feel consistent whether you meet them in Season 1 of the anime or a limited-time event three years into the game’s lifecycle.

Locking characters to specific ages would force every adaptation to synchronize timelines precisely. That’s manageable for a single anime cour, but disastrous for a franchise designed to scale.

Undefined ages act like shared hitboxes across media. Everyone interacts with the same character model, regardless of format, without needing timeline reconciliation.

Real-World Racing History Shapes Birthdays, Not Ages

Birthdays are non-negotiable because they’re anchored to real racehorses. Changing them would sever the franchise’s historical backbone and undermine its tribute-driven identity.

Ages, however, don’t translate cleanly from horse to character. Real racehorses have short competitive lifespans, retire early, and don’t align with long-form character arcs or school narratives.

Cygames locks the stat that matters for authenticity and leaves the one that would break immersion deliberately unassigned.

Player Projection Is a Feature, Not a Side Effect

Leaving ages undefined lets players read characters through personality, voice direction, and narrative role without contradicting canon. A player can see one character as older, another as younger, and neither interpretation breaks the rules.

This flexibility fuels fan discussion, art, and community theorycrafting without forcing official validation. From a design standpoint, that’s free engagement with zero lore maintenance cost.

In gacha terms, undefined age is pure value. It maximizes emotional resonance while minimizing canon risk.

Developer Silence Is Intentional and Consistent

Across in-game profiles, official guidebooks, interviews, and promotional materials, ages are never “forgotten.” They’re consistently omitted.

That level of consistency only happens when something is intentionally excluded. If ages were meant to exist, they would have surfaced somewhere by now.

The absence itself is canon. Umamusume characters have birthdays, personalities, histories, and growth arcs, but age is not a tracked stat in this universe, and that’s by design.

Special Cases and Exceptions: Transfer Students, Senior-Class Implications, and Real Horse References

Even with developer silence established as intentional, some edge cases keep popping up in community debates. Transfer students, upperclassmen vibes, and real-world racing timelines all look like age indicators at first glance. In practice, none of them override the core rule: birthdays are canon, ages are not.

Understanding why these exceptions don’t break the system is key to reading Umamusume lore correctly.

Transfer Students Do Not Indicate Age Differences

Transfer students like Oguri Cap are often misread as being older because they enter the academy later. In traditional anime logic, a mid-year transfer usually flags an age gap or a repeated year. Umamusume deliberately rejects that shorthand.

Oguri Cap’s transfer is about background and racing history, not chronology. She comes from a regional circuit, not a different age bracket, and the narrative treats her as academically and physically aligned with her peers.

From a game design perspective, transfer status is a flavor stat, not a level indicator. It adds texture to character arcs without introducing timeline friction or forcing an age value into the profile.

“Senior” Presence Is a Role, Not a Number

Some characters read as clearly more mature, more composed, or more authoritative. Fans often label them as seniors or upperclassmen, especially when they act as mentors or team anchors. That interpretation is supported tonally, but never numerically.

The academy setting uses class standing as a narrative role, similar to party positioning in an RPG. A character can tank emotional pressure, manage team morale, or act as a shot-caller without being older in years.

Crucially, no in-game profile, event text, or anime material ever assigns a grade year or age. Seniority exists as soft storytelling aggro, not as a tracked stat.

Graduation Arcs Still Avoid Hard Ages

Anime seasons and story events occasionally reference advancement or graduation. This is where many players expect ages to finally lock in. They never do.

Graduation functions as a progression gate, not a birthday trigger. Characters move forward in their careers without the story ever stating how old they are before or after that transition.

It’s the same design logic as a level cap increase without showing EXP totals. You feel growth, but the math stays hidden to protect flexibility across future content.

Real Horse Eras Don’t Translate to Character Ages

Another common pitfall is mapping real horse racing eras directly onto character age assumptions. Horses from older generations competed earlier, so players assume their Umamusume counterparts must be older too. That’s not how the adaptation works.

Real horses anchor birthdays and historical achievements, not lifespans. A horse born in the 1980s informs a character’s racing legacy, not her age within the academy setting.

Cygames cherry-picks what preserves authenticity and discards what would break the school framework. Birthdays stay locked; ages stay abstract.

Confirmed Ages vs. Intentionally Unspecified Ones

As of now, there are no playable Umamusume characters with officially confirmed numerical ages. This includes main story leads, transfer students, and characters portrayed as seniors.

Adult characters outside the student pool, such as trainers or administrative figures, are clearly coded as adults but still lack explicit age numbers. Even here, the franchise avoids hard data unless it’s absolutely necessary.

The pattern is consistent and up to date. If a character has a birthday, it’s canon and traceable to a real horse. If you’re looking for an age, the absence isn’t an oversight—it’s the rule working as intended.

Anime vs Game Canon: Do Adaptations Change Age Interpretation?

With all that groundwork laid, the natural follow-up is whether the anime finally breaks the rules the game refuses to touch. On the surface, anime adaptations feel more concrete, with clearer timelines, seasonal arcs, and visual aging cues. In practice, they follow the same canon logic as the game, just with different camera angles.

The Anime Adds Structure, Not Numbers

The Umamusume anime introduces pacing that looks like time passing. Training seasons change, tournaments resolve, and characters move from rookies to contenders in a way that feels chronological.

What never changes is the absence of hard age data. No episode title card, character profile, or line of dialogue assigns a number. The anime uses progression the same way the game uses story chapters: momentum without math.

Think of it like visible cooldowns without exact frame data. You know something advanced, but you’re not given the raw stats.

Visual Maturity Is Not Aging

A common misconception is that character design tweaks in the anime imply aging. Sharper expressions, more confident body language, or toned-down comedic beats often get read as “they’re older now.”

That’s a narrative buff, not a stat increase. The franchise treats maturity as a skill unlock, not a birthday trigger. Characters gain composure the same way they gain race IQ, without their age ever ticking upward.

If anything, this design avoids hitbox issues across adaptations. A character has to read the same whether you met her in Season 1, Season 3, or the game’s tutorial.

Different Medium, Same Canon Ruleset

Cygames is extremely strict about canon synchronization. The anime does not overwrite the game, and the game does not retroactively reinterpret the anime.

Birthdays remain fixed and traceable to real horses across all media. Ages remain intentionally unspecified across all media. There is no split canon where the anime “confirms” something the game hides.

From a lore standpoint, both versions are running the same ruleset. They just prioritize different storytelling DPS.

Why Adaptations Avoid Locking Ages

Locking numerical ages would create long-term balance problems. Once you assign a character a number, every future story, collab, or seasonal event has to respect that timeline.

By keeping ages abstract, Cygames preserves RNG-friendly flexibility. Characters can headline a new anime season, return in a live event, or anchor a fresh game arc without timeline aggro.

This is the same philosophy behind not showing exact EXP totals. The system works because it stays invisible.

What Players Should Treat as Canon

For players compiling a definitive list, the rule is simple. Birthdays are 100 percent canon and identical across anime and game. They come directly from real-world racehorse data and never change.

Ages, on the other hand, are universally unconfirmed. If a character appears younger, older, senior, or rookie, that is a narrative role, not a measurable stat.

No adaptation overrides this. If you can’t find an age number, it’s not missing data—it’s protected canon.

Complete Reference Table: All Umamusume Characters’ Birthdays and Canonical Age Status

With the canon ruleset locked in, this is where theorycrafting stops and hard data begins. Birthdays are fixed, verifiable, and identical across the game, anime, and live events. Age values, meanwhile, are deliberately left off the stat sheet for every single character.

To make this crystal clear for roster planners, lore archivists, and anniversary grinders, the table below lists each Umamusume’s official birthday alongside her canonical age status as defined by Cygames.

How to Read This Table Without Overthinking It

If you’re looking for a number under “Age,” you won’t find one. That’s not missing data or a localization gap; it’s a protected design choice. Every entry shares the same age classification because the system treats age as a narrative role, not a measurable stat.

Birthdays, on the other hand, are 1:1 mappings from the real racehorses. These dates never change and are safe to use for login bonuses, merch drops, and event speculation.

All Umamusume Characters: Birthday and Canonical Age Status

This same rule applies to the extended roster introduced through later game updates, anime seasons, and live-service expansions. No Umamusume, playable or otherwise, has an officially published numerical age.

Why Every Entry Shares the Same Age Status

From a balance perspective, this keeps the entire roster future-proof. Characters can rotate between rookie arcs, veteran mentorship roles, and championship storylines without triggering timeline contradictions or power creep debates.

From a lore perspective, it reinforces the academy setting as a static battlefield. Like a fighting game stage or a MOBA map, the environment persists while matchups and narratives rotate in and out.

The Practical Takeaway for Players and Fans

If you’re tracking birthdays, you’re playing with confirmed, immutable data. If you’re debating ages, you’re stepping outside the hitbox of canon and into headcanon territory.

Treat birthdays as real stats. Treat age as flavor text that never resolves into a number. That’s not a limitation—it’s the system working as intended.

And once you internalize that, Umamusume’s lore stops feeling vague and starts feeling elegantly optimized for the long race ahead.