Ølstykke FC
















































Ølstykke FC
Ølstykke FC.png
Full name Ølstykke Fodbold Club
Short name ØFC
Founded May 18, 1918 (1918-05-18)
Ground
Ølstykke Stadion,
Ølstykke
Capacity 3,000 (400 seats)
Chairman Jimmy Bernard
Manager Morten Agerbæk
League Series 3
2010–11 Series 1, pool 1, 4th

















Home colours













Away colours



Ølstykke FC is a Danish football club, from the small town of Ølstykke on Sjælland.


The club was founded on 18 May 1918 as Ølstykke Idrætsforening; the club was also playing basketball. In 1986, the name was changed to Ølstykke FC as the club wanted to focus solely on football.




Contents






  • 1 Honours


  • 2 Season-by-season results


  • 3 See also


  • 4 External links





Honours




  • Danish Champions
    • Winner (0):



  • Danish Cup

    • Winner (0):


    • Best result: Semifinal (1990)





Season-by-season results















































































































Season
 Pos
 Pts
 Pld
 W
 D
 L
 GF
 GA
 GD
05-06: Viasat Sport Divisionen (pending)
 #11/16 19 15 5 4 6 18 20 −2
04-05: Viasat Sport Divisionen
 #13/16 30 30 8 6 16 39 68 −29
03-04: 1. Division
 #7/16 43 30 13 4 13 59 53 +6
02-03: 1. Division
 #8/16 41 30 11 8 11 65 61 +4

01-02: 2. Division
 #2/16 59 30 18 5 7 60 32 +28

00-01: Faxe Kondi Divisionen
 #15/16 30 30 8 6 16 38 76 −38
99-00: Faxe Kondi Divisionen
 #10/16 36 30 9 9 12 42 60 −18

98–99: 2. Division
 #3/16 51 30 13 9 8 72 52 +20

Green denotes promotion, red denotes relegation.



See also


  • FC Egedal


External links



  • Official website (in Danish)







-

Popular posts from this blog

SQL Server 17 - Attemping to backup to remote NAS but Access is denied

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0; } 0 I was attemping to use Ola Hallengrens scripts to backup to a remote NAS, but it was failing and not giving any direct errors, so I tried doing it manually using Server Management Studio and got the following error: TITLE: Microsoft SQL Server Management Studio Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476 ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) The operating system returned the error '0x80070005(Access is denied.)&#
Read more

Always On Availability groups resolving state after failover - Remote harden of transaction...

Image
0 My explanation will be opinion based as it is based on my findings. If more information is needed, I am always happy to add it. The setup We have 4 SQL Server 2016 Instances, and all 4 underlying servers are in a WSFC (In my eyes a strange setup since Always On AG's are 2 by 2. But that is a different question.) 4 nodes + Fileshare witness Version: 13.0.5026.0 (all nodes) The instances that are having the failover issues are instances 1 & 2. They have 3 AG's between them. AG1 is primary on instance 1 and is having the issue. AG2 and AG3 are primary on instance 2. Instances 3 and 4 have their own separate AG's (2). AG1's settings The week before Last week, after checking for long running queries (none) and the synchronization state (green accross the board) we initiated a
Read more

Restoring from pg_dump with foreign key constraints

Image
5 2 In restoring a database from a pg_dump , a number of errors are being generated and the whole table is subsequently being ignored. An example: ERROR: insert or update on table "channelproducts" violates foreign key constraint "fk_rails_dfaae373a5" DETAIL: Key (channel_id)=(1) is not present in table "channels". Interestingly enough, I've noted that all these instances are popping up because of the sequence of loading. channels is after channelproducts both alphabetically and in the file and thus I can understand why postgres complains about having to create a child without a parent. caveat: the foreign key is being generated automatically by rails 4.2: I could remove the problem at the source but that still does not really solve the problem... version: PostgreSQL
Read more