Tinker Bell - Giant Fairy
Printing 9:188 · Fabled № 188 · Super Rare ·
card concept Tinker Bell - Giant Fairy
enfrdeit printed identifier 188/204 • EN • 9
Verified original 1468×2048 JPEG, sha256 d861ba8458fe…
Printed on this card
Shift 4 (You may pay 4 ⬡ to play this on top of one of your characters named Tinker Bell.)
ROCK THE BOAT When you play this character, deal 1 damage to each opposing character.
PUNY PIRATE! During your turn, whenever this character banishes another character in a challenge, you may deal 2 damage to chosen opposing character.
- Rarity
- Super Rare
- Type
- Character
- Ink
- Steel
- Classifications
- Floodborn · Ally · Fairy
- Foil
- Silver
- Artist
- Cookie
- Story
- Peter Pan
How it is obtained
- Set
- Fabled (expansion), released 5 September 2025
- Tournament legal from
Legality of this printing
Core Constructed: legalInfinity Constructed: legal
A rotated printing stays legal while the card name is in a legal set; see the card concept for the roll-up. Source: LorcanaJSON legality data from the Tournament Rules.
Same card, other printings
| Key | Set | Released | Rarity · foil | Artist | Languages |
|---|---|---|---|---|---|
| 1:193 | The First Chapter | Super Rare · Silver | Cookie | en fr de | |
| 1:216 | The First Chapter | Enchanted · Lava | Cookie | en fr de | |
| CC1:6 | Curator's Collection: Heroines Edition · Curator's Collection: Heroines Edition | Special · Satin | Kim Kha | en | |
| Coconut:15 | [Format Coconut] · Format Coconut (beta) · beta-format version, different text | — | Cookie | en | |
| P3:11 | Promo Set 3 · 'Fabled' Collection Starter Set | Special · Glitter | Cookie | en fr de it |
Relations recorded upstream: Promo printing CC1:6 · Promo printing P3:11 · Reprint of 1:193
Same artwork as 1:193, Coconut:15, P3:11 (image similarity, computed — not a sourced fact).
Identifiers and provenance
- Lorbrarian
9:188·/sets/9/188- LorcanaJSON
2124· code yg- Lorcast
crd_a77ba07844374c399becfa3d49262642- TCGplayer
650121- Cardmarket
844141- CardTrader
332055- Sources
- lorcanajson + lorcast · matched by exact · no field conflicts
Something wrong? Corrections go through the data pipeline, never a page edit — a report form arrives in Phase 4; until then see About.