BIZTRAC BETA
COMPANY REGISTER PROFILE
981061225 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

LARSEN EIENDOM AS

Org. no. 981061225 Limited company (AS) Drammen Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 129,000
Operating profit NOK 15,000
Equity NOK 4.0m
Incorporated 1999
Share capital NOK 100,000

LARSEN EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 981061225. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Handel, drift og utvikling av fast eiendom samt deltagelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 129,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 129,000
Operating profit
NOK 15,000
Equity
NOK 4.0m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns LARSEN EIENDOM AS?

PER ARVID BERG LARSEN
LARSEN EIENDOM AS
NOK 129,000 rev. · NOK 15,000 profit

LARSEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LARSEN EIENDOM AS

Who owns LARSEN EIENDOM AS?

PER ARVID BERG LARSEN is the largest registered owner, with 100.0%.

What is the revenue of LARSEN EIENDOM AS?

LARSEN EIENDOM AS had revenue of NOK 129,000 in 2024.

Who is the general manager of LARSEN EIENDOM AS?

Per Arvid Berg Larsen is registered as general manager of LARSEN EIENDOM AS.

Where is LARSEN EIENDOM AS based?

LARSEN EIENDOM AS has its business address in Svelvik.

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.