2013 Samsung Securities Cup – Women's Singles

Erika Sema was the defending champion, having won the event in 2012, but chose not to compete in 2013.

Women's Singles
2013 Samsung Securities Cup
Champion	Han Na-lae
Runner-up	Kim Da-hye
Final score	6–4, 6–4

Han Na-lae won the tournament, defeating Kim Da-hye in the all-Korean final, 6–4, 6–4.

Seeds

Eri Hozumi (first round)
Junri Namigata (first round)
Shuko Aoyama (second round)
Nudnida Luangnam (second round)
Liu Fangzhou (first round)
Deniz Khazaniuk (second round)
Nao Hibino (quarterfinals)
Jang Su-jeong (quarterfinals)

Main draw

Key

Finals

	Semifinals							Final


		Han Na-lae	6⁴	6	6

		Varvara Flink	7⁷	3	2
									Han Na-lae	6	6

								Q	Kim Da-hye	4	4
	Q	Kim Da-hye	6	7

		Lee So-ra	3	5

Top half

	First round							Second round							Quarterfinals							Semifinals

	1	E Hozumi	6	5	6⁴
	Q	S-y Hong	1	7	7⁷			Q	S-y Hong	2	2
		Y-r Lee	6	6					Y-r Lee	6	6
		A Omae	4	0												Y-r Lee	6	2^r
		B Bonić	6	0	1											N-l Han	4	5
		S Akita	2	6	6				S Akita	4	2
		N-l Han	4	6	6				N-l Han	6	6
	5	F Liu	6	3	3																		N-l Han	6⁴	6	6
	3	S Aoyama	6	6																			V Flink	7⁷	3	2
		Y Sizikova	3	2				3	S Aoyama	4	6	1
		V Flink	6	6					V Flink	6	1	6
		M Kato	2	0												V Flink	6	6
	Q	R Fujiwara	0^r												8	S-j Jang	4	3
	WC	M-h Yu	4					WC	M-h Yu	1^r
	WC	H Lee	1	0				8	S-j Jang	4
	8	S-j Jang	6	6

Bottom half

	First round							Second round							Quarterfinals							Semifinals

	6	D Khazaniuk	6	6
	WC	S-h Han	1	4				6	D Khazaniuk	5	2
	Q	S-j Kim	5	3					J Lu	7	6
		J Lu	7	6												J Lu	6	2	5
	Q	Y-w Jeong	3	2											Q	D-h Kim	2	6	7
	Q	D-h Kim	6	6				Q	D-h Kim	6	6
		K Lehnert	6	0	6¹			4	N Luangnam	4	2
	4	N Luangnam	4	6	7⁷																	Q	D-h Kim	6	7
	7	N Hibino	6	6																			S-r Lee	3	5
	Q	L Zhu	1	4				7	N Hibino	6	6
	Q	J-h Choi	6	6				Q	J-h Choi	2	2
	Q	S-j Kim	4	3											7	N Hibino	7	2	6³
	WC	S-k Kang	6	4	3											S-r Lee	5	6	7⁷
		M Miyamura	1	6	6				M Miyamura	6³	1
		S-r Lee	7	6					S-r Lee	7⁷	6
	2	J Namigata	5	2

gollark: Not inherently. It is entirely possible to write horribly coupled OOP, especially since it encourages apious mutable state and inheritance.

gollark: ++remind 41w lyric bad

gollark: ++remind 17mo33d lyric bad

gollark: ++remind 6mo lyric bad

gollark: Indeed.

References

Main draw

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.