1995–96 Azadegan League

The following is the final results of the Azadegan League's 1995/96 football season.

Azadegan League
Season1995–96
ChampionsPersepolis
RelegatedJonoob Ahvaz
Ararat Tehran
Shahrdari Tabriz
Saipa
Asian Club ChampionshipPersepolis
Asian Winners' CupEsteghlal
Matches played240
Goals scored483 (2.01 per match)
Top goalscorerMohammad Momeni (19)

League table

Pos Team Pld W D L GF GA GD Pts Qualification or relegation
1 Persepolis (C) 30 15 12 3 33 18 +15 57 Qualification for the 1996–97 Asian Club Championship
2 Bahman 30 13 12 5 47 24 +23 51
3 Esteghlal 30 14 9 7 41 26 +15 51 Qualification for the 1996–97 Asian Cup Winners' Cup
4 PAS 30 13 6 11 33 35 2 45
5 Sepahan 30 11 9 10 40 34 +6 42
6 Bargh Shiraz 30 11 9 10 32 26 +6 42
7 Esteghlal Ahvaz 30 12 5 13 40 41 1 41
8 Machine Sazi 30 11 8 11 35 38 3 41
9 Keshavarz 30 9 13 8 32 25 +7 40
10 Polyacryl 30 10 8 12 33 39 6 38
11 Shamoushak Noshahr 30 10 8 12 28 38 10 38
12 Malavan 30 9 10 11 21 25 4 37
13 Jonoob Ahvaz (R) 30 9 9 12 26 39 13 36 Relegation to the 1996–97 Iran 2nd Division
14 Ararat Tehran (R) 30 8 7 15 27 39 12 31
15 Sh. Tabriz (R) 30 6 10 14 24 34 10 28
16 Saipa (R) 30 5 13 12 31 42 11 28
Updated to match(es) played on 01 SEP 2018. Source: RSSSF
Rules for classification: 1) Points; 2) Goal difference; 3) Goals scored.
(C) Champion; (R) Relegated.

Top goal scorer

Mohammad Momeni (Poli Ekril Isfahan) (19 goals)

gollark: Okay, very hacky but technically workable: have an XTMF metadata block of a fixed size, and after the actual JSON data, instead of just ending it with a `}`, have enough spaces to fill up the remaining space then a `}`.
gollark: XTMF was not really designed for this use case, so it'll be quite hacky. What you can do is leave a space at the start of the tape of a fixed size, and stick the metadata at the start of that fixed-size region; the main problem is that start/end locations are relative to the end of the metadata, not the start of the tape, so you'll have to recalculate the offsets each time the metadata changes size. Unfortunately, I just realized now that the size of the metadata can be affected by what the offset is.
gollark: The advantage of XTMF is that your tapes would be playable by any compliant program for playback, and your thing would be able to read tapes from another program.
gollark: Tape Shuffler would be okay with it, Tape Jockey doesn't have the same old-format parsing fallbacks and its JSON handling likely won't like trailing nuls, no idea what tako's program thinks.
gollark: Although I think some parsers might *technically* be okay with you reserving 8190 bytes for metadata but then ending it with a null byte early, and handle the offsets accordingly, I would not rely on it.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.