biztrac. BETA
COMPANY REGISTER PROFILE
920168868 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

VILBERGSKOGEN AS

Org. no. 920168868 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 17.2m
Operating profit NOK 4.3m
Equity NOK −11.6m
Incorporated 2017
Share capital NOK 50,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11,6 mill kr).

VILBERGSKOGEN AS is registered as a limited company in Oslo, Oslo with organisation number 920168868. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Kjøp, utvikling, salg og utleie av fast eiendom og andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.2m in revenue and NOK 4.3m in operating profit.

Key figures · 2025

Revenue
NOK 17.2m
▲ +0 %
Operating profit
NOK 4.3m
▲ +0 %
Equity
NOK −11.6m
▲ +0 %
Est. value
NOK 22.7m

Financial health · 2025

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-66.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VILBERGSKOGEN AS?

VILBERGSKOGEN AS
NOK 17.2m rev. · NOK 4.3m profit

VILBERGSKOGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VILBERGSKOGEN AS

Who owns VILBERGSKOGEN AS?

MARIENDAL EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of VILBERGSKOGEN AS?

VILBERGSKOGEN AS had revenue of NOK 17.2m in 2025.

Where is VILBERGSKOGEN AS based?

VILBERGSKOGEN 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 03.10.2026.

Report a problem

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