BIZTRAC BETA
Rental and operating of own or leased real estate

ROAR LUND EIENDOM AS

Org. no. 881693062 Limited company (AS) Drammen Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 360,000
Operating profit NOK 316,000
Equity NOK 1.3m
Incorporated 2000
Share capital NOK 190,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ROAR LUND EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 881693062. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 190,000, divided into 100 shares. The company's stated purpose is: “Uvikling, forvaltning og handel med fast eiendom, samt hva hermed står i forbindelse, herunder å delta i selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 360,000 in revenue and NOK 316,000 in operating profit.

Key figures · 2025

Revenue
NOK 360,000
Operating profit
NOK 316,000
Equity
NOK 1.3m
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
9.44
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
90.7%
Very good
Equity as a share of total capital

Who owns ROAR LUND EIENDOM AS?

GREWA HOLDING AS
ROAR LUND EIENDOM AS
NOK 360,000 rev. · NOK 316,000 profit

ROAR LUND EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROAR LUND EIENDOM AS

Who owns ROAR LUND EIENDOM AS?

GREWA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ROAR LUND EIENDOM AS?

ROAR LUND EIENDOM AS had revenue of NOK 360,000 in 2025.

Where is ROAR LUND EIENDOM AS based?

ROAR LUND EIENDOM AS has its business address in Drammen.

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.