Na Jung-woong

Na Jung-woong (Korean: 나정웅; born 31 October 1992) is a South Korean tennis player.

Na Jung-woong
나정웅
Country (sports) South Korea
Born (1992-10-31) 31 October 1992
Prize money$47,400
Singles
Career record0–1 (at ATP Tour level, Grand Slam level, and in Davis Cup)
Career titles1 ITF
Highest rankingNo. 404 (16 September 2013)
Doubles
Career record0–0 (at ATP Tour level, Grand Slam level, and in Davis Cup)
Career titles0 ITF
Highest rankingNo. 966 (19 May 2014)
Last updated on: 15:11, 3 July 2019 (UTC).
Na Jung-woong
Hangul
나정웅
Revised RomanizationNa Jeongung
McCune–ReischauerNa Chŏngung

Na has a career high ATP singles ranking of 404 achieved on 16 September 2013. He also has a career high ATP doubles ranking of 966 achieved on 19 May 2014.

Na represents South Korea at the Davis Cup, where he has a W/L record of 0–1.

Challengers and Futures finals

Singles (1–5)

Legend
ATP Challenger Tour (0–0)
ITF Tour (1–5)
Titles by Surface
Hard (1–4)
Clay (0–1)
Grass (0–0)
Outcome Date Tournament Surface Opponent Score
Runner-up 5 May 2013 Seoul, South Korea Hard Daniel Nguyen 1–6, 4–6
Runner-up 24 November 2013 Bhopal, India Hard Sriram Balaji 5–7, 5–7
Winner 16 August 2015 Gimcheon, South Korea Hard Chung Yun-seong 6–3, 6–1
Runner-up 23 August 2015 Gimcheon, South Korea Hard Yusuke Watanuki 5–7, 3–6
Runner-up 6 September 2015 Anseong, South Korea Clay Cho Min-hyeok 7–6, 2–6, 4–6
Runner-up 9 June 2019 Daegu, South Korea Hard Hong Seong-chan 0–6, 3–6

Doubles (0–1)

Legend
ATP Challenger Tour (0–0)
ITF Tour (0–1)
Titles by Surface
Hard (0–0)
Clay (0–1)
Grass (0–0)
Outcome Date Tournament Surface Partner Opponent Score
Runner-up 25 January 2015 Cairo, Egypt Clay Yun Jae-won Maxime Janvier
Kamil Majchrzak
2–6, 2–6
gollark: Yes, *that's* ridiculous, but sometimes it isn't.
gollark: JS actually is faster than python generally.
gollark: Or you write still less-performant high-level code, which is what you actually need most of the t ime.
gollark: Assembly is obviously better for... I don't know, when you actually need to implement interrupt handlers or something, or when you have a small bit of computing which needs to be run as fast as possible, but most practical stuff is *not* that.
gollark: Actually, it might be better to write it as OpenCL if it parallelizes well enough to run on GPUs.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.