Catalogus
Volledige afbeeldingen bekijken — gratis registratie
Doorgaan met Google — het is gratis
of registreer met e-mail
Waarom registreren? Alleen om bots buiten ons catalogus te houden. Uw e-mail blijft privé — we delen het nooit en sturen u niets zonder uw toestemming. Dat garanderen wij u!
1000 Rupees
| Uitgever | Bank of Mauritius |
|---|---|
| Jaar | 1999-2007 |
| Type | Standard circulation banknote |
| Waarde | Log in om details te zien |
| Valuta | Log in om details te zien |
| Samenstelling | Log in om details te zien |
| Afmetingen | Log in om details te zien |
| Vorm | Log in om details te zien |
| Drukker | Log in om details te zien |
| Ontwerper(s) | Log in om details te zien |
| Graveur(s) | Log in om details te zien |
| In omloop tot | Log in om details te zien |
| Referentie(s) | Log in om details te zien |
| Beschrijving voorzijde | Log in om details te zien |
|---|---|
| Opschrift voorzijde | BANK OF MAURITIUS ONE THOUSAND RUPEES Rs1000 THIS NOTE IS LEGAL TENDER FOR SIR CHARLES GAETAN DUVAL QC 1930-1996 GOVERNOR MANAGING DIRECTOR ஆயிரம் ரூபாய் एक हज़ार रुपये |
| Beschrijving keerzijde | Log in om details te zien |
| Opschrift keerzijde | Log in om details te zien |
| Handtekening(en) | Log in om details te zien |
| Beveiligingstype | Log in om details te zien |
| Beschrijving beveiliging | Sir Charles Gaetan Duval portrait visible when held to light; embedded security thread running vertically through the note |
| Varianten | Log in om details te zien |
| Opmerkingen |
The 1000 Rupee denomination was the highest value note in Mauritian circulation during this period, and De La Rue's involvement was continuous across the entire series — the same London relationship the Bank of Mauritius had maintained since independence. Three distinct signature combinations across eight years reflect the turnover at the top of the central bank: Bheenick replaced Ring as Governor in 2007, while Manraj's presence as Second Governor across all variants gives the series an unusual continuity at one post.
P#54 is sometimes found with ink migration on the security thread under UV — not an error as such, but worth noting on high-grade examples.