SetsUrsula's Return№ 146French

Hans - Noble crapule Printing 4:146 · Ursula's Return № 146 · Common · card concept Hans - Noble Scoundrel

enfrdeit printed identifier 146/204 • FR • 4

Hans - Noble crapule — Ursula's Return 146 (French)
Illustrated by Dustin Panzino and Leonardo Giammichele · image © Disney / Ravensburger, shown whole and uncropped

Verified original 1468×2048 JPEG, sha256 15523169c818…

Printed on this card

Sapphire Character Cost 3 · inkable 3 strength 2 willpower 2 lore

INTRIGUES ROYALES S'il y a un personnage Princesse ou Reine en jeu lorsque vous jouez ce personnage, gagnez 1 éclat de Lore.

Hans était persuadé de pouvoir amener Anna à Ursula. Tout ce dont il avait besoin était quelque chose appartenant à Kristoff pour la leurrer.

Errata and earlier wordings

Wording used until 23 August 2024: INTRIGUES ROYALES Si vous avez un personnage Princesse ou Reine en jeu lorsque vous jouez ce personnage, gagnez 1 éclat de Lore. LorcanaJSON allCards.json (fr), formatVersion 2.3.5

Rarity
Commune (Common)
Type
Personnage
Ink
Saphir
Classifications
Storyborn · Méchant · Prince
Foil
Silver
Artist
Dustin Panzino / Leonardo Giammichele
Story
La Reine des neiges

How it is obtained

Set
Ursula's Return (expansion), released 31 May 2024
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

KeySetReleasedRarity · foilArtistLanguages
9:148 Fabled Common · Silver Dustin Panzino / Leonardo Giammichele en fr de it

Relations recorded upstream: Reprinted as 9:148

Same artwork as 9:148 (image similarity, computed — not a sourced fact).

Identifiers and provenance

Lorbrarian
4:146 · /sets/4/146/fr
LorcanaJSON
837 · code dv
Lorcast
crd_9b50f321f3a44275b82b5e49b6766c7c
TCGplayer
543914
Cardmarket
767824
CardTrader
282826
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.