2013–14 Lithuanian Handball League
The 2013–14 Lithuanian Handball League season was the 25th season of the Lithuanian Handball League, the top level handball in Lithuania. Nine teams participated in the league. League started at 11 September 2013 and finished on 10 May 2014.[1]
| Tournament details | |
|---|---|
| Host country |  |
| Dates | 11 September 2013 - 10 May 2014 |
| Teams | 9 |
| Venue(s) | 11 (in 7 host cities) |
| Tournament statistics | |
| Matches played | 93 |
| Goals scored | 5151 (55.39 per match) |
Regular season
Almeida-Stronglasas Alytus
Ūla Varėna
SM Dubysa-Gubernija
HC Utena
Lūšis Kaunas
Location of teams in the 2013-2014 Lithuanian Handball League
| Club | GP | W | D | L | GF | GA | DF | Pts | |
|---|---|---|---|---|---|---|---|---|---|
| 1st | Dragūnas Klaipėda | 16 | 13 | 1 | 2 | 498 | 404 | +94 | 27 |
| 2nd | Almeida-Stronglasas Alytus | 16 | 11 | 2 | 3 | 434 | 367 | +67 | 24 |
| 3rd | VHC Šviesa | 16 | 11 | 1 | 4 | 487 | 440 | +47 | 23 |
| 4th | Ūla Varėna | 16 | 10 | 1 | 5 | 452 | 392 | +60 | 21 |
| 5th | Granitas Kaunas | 16 | 9 | 0 | 7 | 472 | 434 | +38 | 18 |
| 6th | HC Vilnius | 16 | 6 | 1 | 9 | 451 | 461 | -10 | 13 |
| 7th | Lūšis Kaunas | 16 | 5 | 1 | 10 | 416 | 479 | -63 | 11 |
| 8th | SM Dubysa-Gubernija | 16 | 3 | 1 | 12 | 430 | 487 | -57 | 7 |
| 9th | HC Utena | 16 | 0 | 0 | 16 | 419 | 595 | -176 | 0 |
Playoffs
Quarterfinals
- (1) Dragūnas Klaipėda - (8) SM Dubysa-Gubernija (29:22, 32:17)
- (2) Almeida-Stronglasas Alytus - (7) Lūšis Kaunas (21:16, 32:22)
- (3) VHC Šviesa - (6) HC Vilnius (32:26, 27:16)
- (4) Ūla Varėna - (5) Granitas Kaunas (21:26, 23:16, 21:28)
Semifinals
- (1) Dragūnas Klaipėda - (5) Granitas Kaunas (29:26, 29:30, 31:25)
- (2) Almeida-Stronglasas Alytus - (3) VHC Šviesa (27:31, 32:22, 20:28)
3rd place game
- (5) Granitas Kaunas - (2) Almeida-Stronglasas Alytus (28:25, 25:26, 25:26)
Final
- (1) Dragūnas Klaipėda - (3) VHC Šviesa (36:29, 30:28, 30:27)
Attendance: 1,355 (450 per match)
gollark: > 5. .net platform is cracker / hacker friendly Any program running on the client can INEVITABLY be reverse-engineered. Do not rely on it not experiencing that, because you will fail.
gollark: > 4. XAML - the incredibly messy UI technologyPerhaps, but this is not a *language* thing.
gollark: > 3. Garbage collector and memory leak detection tools?Again, not sure if anyone actually runs into this sort of issue in practice.
gollark: > 1. Performance penalties.> [some rambling about C++].NET is generally pretty much *fast enough*. If your application somehow hits performance bottlenecks, rewrite the slow bits in native code, don't just immediately take a development speed hit.> 2. Need to interoperate with C++ / Native (Windows) API’sI don't know how often you actually need to bind to a native API not wrapped by .NET or a third-party library, but you can do it, it's just annoying - but probably less than using C++ for everything!
gollark: This is outrageous pro-C++ anti-C# propaganda.
References
External links
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.