BIZTRAC BETA
Other real estate activities on a fee or contract basis

GARDERBAKKEN AS

Org. no. 822556302 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −7,000
Equity NOK 3.6m
Incorporated 2019
Share capital NOK 200,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GARDERBAKKEN AS is registered as a limited company in Oslo, Oslo with organisation number 822556302. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2019. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte fast eiendom, herunder deltakelse i selskaper med lignende formål samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −7,000
Equity
NOK 3.6m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns GARDERBAKKEN AS?

FET SPAREFORENING AS
GARDERBAKKEN AS
NOK 1.2m rev. · NOK −7,000 profit

GARDERBAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GARDERBAKKEN AS

Who owns GARDERBAKKEN AS?

FET SPAREFORENING AS is the largest registered owner, with 100.0%.

What is the revenue of GARDERBAKKEN AS?

GARDERBAKKEN AS had revenue of NOK 1.2m in 2025.

Where is GARDERBAKKEN AS based?

GARDERBAKKEN AS has its business address in Oslo.

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.