New Zealand at the Deaflympics
New Zealand has been participating at the Deaflympics since 1957. New Zealand has earned about 18 medals at the Deaflympic Games.[1]
New Zealand at the Deaflympics | |
---|---|
IPC code | NZL |
NPC | Deaf Sports New Zealand |
Website | www |
Medals |
|
New Zealand has also competed at the Winter Deaflympics on two occasions, in 1987 and in 1991.
Medal tallies
Summer Deaflympics
Event | Gold | Silver | Bronze | Total |
---|---|---|---|---|
1957 | 0 | 0 | 0 | 0 |
1961 | 0 | 1 | 1 | 2 |
1965 | 0 | 0 | 1 | 1 |
1969 | 0 | 0 | 0 | 0 |
1973 | 0 | 0 | 0 | 0 |
1977 | 0 | 0 | 0 | 0 |
1981 | 1 | 2 | 0 | 3 |
1985 | 2 | 1 | 0 | 3 |
1989 | 1 | 2 | 4 | 7 |
1993 | 0 | 0 | 0 | 0 |
1997 | 0 | 0 | 0 | 0 |
2001 | 0 | 0 | 0 | 0 |
2005 | 0 | 0 | 0 | 0 |
2009 | 1 | 0 | 1 | 2 |
2013 | 0 | 0 | 0 | 0 |
gollark: https://a.gh0.pw/3
gollark: I mean making good use of the DNS packets, not CPU use on each end; I don't really care about that.
gollark: So you probably need checksums now and you use up even more of the packet size.
gollark: And you also need to be able to autodetect properties of the system of DNS servers between you and the authoritative one doing the actual bridging. But that might randomly change (e.g. if you switch network) and start messing up your data.
gollark: But you also want to be able to send data up efficiently, but you're probably using much of the limited space for user data which won't get munged by recursive DNS/proxies/whatever on the session token and whatever, so now you have to deal with *that*.
References
- "Countries | Deaflympics". www.deaflympics.com. Archived from the original on 2017-10-08. Retrieved 2017-09-19.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.