BIZTRAC BETA
Other recreational activities

MIKLAGARD GOLFDRIFT AS

Org. no. 932736144 Limited company (AS) Ullensaker Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 21.9m
Operating profit NOK −4.3m
Equity NOK 196,000
Incorporated 2023
Employees 12
Share capital NOK 4.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,3 mill kr).

MIKLAGARD GOLFDRIFT AS is registered as a limited company in Ullensaker, Akershus with organisation number 932736144. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 2023 and has 12 registered employees. Registered share capital is NOK 4.0m, divided into 400000 shares. The company's stated purpose is: “Å forestå drift av Miklagard golfbane.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.9m in revenue and NOK −4.3m in operating profit.

Key figures · 2024

Revenue
NOK 21.9m
Operating profit
NOK −4.3m
Equity
NOK 196,000
Est. value
NOK 16.7m

Financial health · 2024

Liquidity
1.91
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.3%
Not satisfactory
Equity as a share of total capital

Who owns MIKLAGARD GOLFDRIFT AS?

GOLF HOLDING AS
MIKLAGARD GOLFDRIFT AS
NOK 21.9m rev. · NOK −4.3m profit

MIKLAGARD GOLFDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MIKLAGARD GOLFDRIFT AS

Who owns MIKLAGARD GOLFDRIFT AS?

GOLF HOLDING AS is the largest registered owner, with 92.3%.

What is the revenue of MIKLAGARD GOLFDRIFT AS?

MIKLAGARD GOLFDRIFT AS had revenue of NOK 21.9m in 2024.

Who is the general manager of MIKLAGARD GOLFDRIFT AS?

Tore Waagø is registered as general manager of MIKLAGARD GOLFDRIFT AS.

Where is MIKLAGARD GOLFDRIFT AS based?

MIKLAGARD GOLFDRIFT AS has its business address in Kløfta.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.