1970 Soviet Class A First Group

The 1970 Soviet Class A First Group was a transitional season of the future Soviet First League. It was also the 30th season of the Soviet second tier league competition.

The league was reduced to a single group in comparison with the previous season.

Final standings
Pos Rep Team Pld W D L GF GA GD Pts Promotion
1 UKR Karpaty Lvov 42 26 11 5 70 22 +48 63 Promoted
2 KAZ Kayrat Alma-Ata 42 25 11 6 71 29 +42 61[lower-alpha 1]
3 UKR Dnepr Dnepropetrovsk 42 26 9 7 58 25 +33 61
4 RUS Lokomotiv Moskva 42 20 10 12 53 39 +14 50[lower-alpha 1]
5 UKR Metallist Kharkov 42 15 19 8 43 26 +17 49
6 RUS Dinamo Leningrad 42 19 9 14 62 49 +13 47
7 RUS Krylya Sovetov Kuibyshev 42 17 13 12 43 32 +11 47[lower-alpha 1]
8 RUS Rubin Kazan 42 18 10 14 36 42 −6 46
9 KAZ Shakhtyor Karaganda 42 15 15 12 49 43 +6 45
10 LTU Žalgiris Vilnius 42 15 11 16 46 40 +6 41
11 MDA Moldova Kishinev 42 13 15 14 40 34 +6 41
12 RUS Textilshchik Ivanovo 42 13 14 15 36 51 −15 40
13 RUS Volgar Astrakhan 42 14 11 17 38 45 −7 39
14 RUS UralMash Sverdlovsk 42 13 12 17 37 49 −12 38[lower-alpha 1]
15 GEO Lokomotiv Tbilisi 42 14 9 19 36 43 −7 37
16 RUS Kuban Krasnodar 42 11 15 16 27 45 −18 37
17 LVA Daugava Riga 42 11 11 20 36 50 −14 33
18 TJK Pamir Dushanbe[lower-alpha 2] 42 12 9 21 41 62 −21 33
19 UKR SKA Kiev 42 11 10 21 39 50 −11 32
20 KGZ Alga Frunze 42 10 12 20 34 45 −11 32
21 RUS SKA Khabarovsk 42 8 16 18 22 41 −19 32
22 TKM Stroitel Ashkhabad 42 6 8 28 22 77 −55 20
Source: rsssf.com
Notes:
  1. -
  2. Pamir Dushanbe was called Energetik.
gollark: * mistakes
gollark: It's an AWFUL tool for dealing with programming mistkaes.
gollark: Well, for a perfect mistake-removing thing yes, but we have things which just *sort of* do that by enforcing some rules, like static typing.
gollark: We've seen *already* exploits in many, many complex things designed by competent programmers. The solution is not "program better and don't make mistakes", you need tools which detect mistakes and/or prevent them.
gollark: Also, if you mess up a surgery and, say, accidentally kill someone, it's more obvious than if your code turns out to have, some years later, had a security hole.

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