BIZTRAC BETA
Rental and operating of own or leased real estate

OLAGARD AS

Org. no. 883598342 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 2.0m
Equity NOK 5.3m
Incorporated 2001
Share capital NOK 1.1m

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-06 Adresseendring registrert 2026-02-06.

OLAGARD AS is registered as a limited company in Oslo, Oslo with organisation number 883598342. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 1.1m, divided into 1100 shares. The company's stated purpose is: “Drive eiendomsutvikling, herunder kjøp, salg, utleie og drift av fast eiendom, investering i andre selskaper og annen virksomhet av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 2.0m
Equity
NOK 5.3m
Est. value
NOK 6.7m

Financial health · 2024

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

Who owns OLAGARD AS?

VINGARD AS
OLAGARD AS
NOK 2.4m rev. · NOK 2.0m profit

OLAGARD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLAGARD AS

Who owns OLAGARD AS?

VINGARD AS is the largest registered owner, with 100.0%.

What is the revenue of OLAGARD AS?

OLAGARD AS had revenue of NOK 2.4m in 2025.

Who is the general manager of OLAGARD AS?

Erling Moberg is registered as general manager of OLAGARD AS.

Where is OLAGARD AS based?

OLAGARD 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.