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

VILTER EIENDOM AS

Org. no. 923810560 Limited company (AS) Oslo Incorporated 2019 Active
Revenue 2025 NOK 3.4m
Operating profit NOK 946,000
Equity NOK 1.8m
Incorporated 2019
Share capital NOK 250,000

VILTER EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 923810560. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 250,000, divided into 20000 shares. The company's stated purpose is: “Investere i aksjer og andre verdipapirer samt investere i fast eiendom og annen virksomhet som naturlig hører hertil.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 946,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
▲ +11 %
Operating profit
NOK 946,000
▼ −12 %
Equity
NOK 1.8m
▼ −28 %
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
2.33
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
2.4%
Not satisfactory
Equity as a share of total capital

Who owns VILTER EIENDOM AS?

VILTER EIENDOM AS
NOK 3.4m rev. · NOK 946,000 profit

VILTER EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VILTER EIENDOM AS own?

VILTER EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VILTER EIENDOM AS

Who owns VILTER EIENDOM AS?

LEVREBEKKEN INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of VILTER EIENDOM AS?

VILTER EIENDOM AS had revenue of NOK 3.4m in 2025.

Where is VILTER EIENDOM AS based?

VILTER EIENDOM 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.