BIZTRAC BETA
Accounting and bookkeeping

REGNSKAP OG EIENDOM AS

Org. no. 920459021 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.0m
Equity NOK 30,000
Incorporated 2018
Share capital NOK 30,000

REGNSKAP OG EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 920459021. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Regnskap og bokføring med dertil følgende tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 1.0m
Equity
NOK 30,000
Est. value
NOK 3.2m

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.7%
Weak
Equity as a share of total capital

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

Who owns REGNSKAP OG EIENDOM AS?

VIDAR LUND
REGNSKAP OG EIENDOM AS
NOK 2.6m rev. · NOK 1.0m profit

REGNSKAP OG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REGNSKAP OG EIENDOM AS own?

REGNSKAP OG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about REGNSKAP OG EIENDOM AS

Who owns REGNSKAP OG EIENDOM AS?

VIDAR LUND is the largest registered owner, with 100.0%.

What is the revenue of REGNSKAP OG EIENDOM AS?

REGNSKAP OG EIENDOM AS had revenue of NOK 2.6m in 2025.

Who is the general manager of REGNSKAP OG EIENDOM AS?

Vidar Lund is registered as general manager of REGNSKAP OG EIENDOM AS.

Where is REGNSKAP OG EIENDOM AS based?

REGNSKAP OG 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 15.06.2026.

Report a problem

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