BIZTRAC BETA
Other real estate activities on a fee or contract basis

ARENA EIENDOM DRIFT AS

Org. no. 992962550 Limited company (AS) Bærum Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 11.5m
Operating profit NOK 106,000
Equity NOK 176,000
Incorporated 2008
Share capital NOK 100,000

ARENA EIENDOM DRIFT AS is registered as a limited company in Bærum, Akershus with organisation number 992962550. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1 shares. The company's stated purpose is: “Drift og forvaltning av fast eiendom, investering i selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.5m in revenue and NOK 106,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.5m
Operating profit
NOK 106,000
Equity
NOK 176,000
Est. value
NOK 340,000

Financial health · 2024

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.6%
Not satisfactory
Equity as a share of total capital

Who owns ARENA EIENDOM DRIFT AS?

ARENA EIENDOM AS
ARENA EIENDOM DRIFT AS
NOK 11.5m rev. · NOK 106,000 profit

ARENA EIENDOM DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARENA EIENDOM DRIFT AS

Who owns ARENA EIENDOM DRIFT AS?

ARENA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ARENA EIENDOM DRIFT AS?

ARENA EIENDOM DRIFT AS had revenue of NOK 11.5m in 2024.

Who is the general manager of ARENA EIENDOM DRIFT AS?

Kjetil Bell Tveit is registered as general manager of ARENA EIENDOM DRIFT AS.

Where is ARENA EIENDOM DRIFT AS based?

ARENA EIENDOM DRIFT AS has its business address in Fornebu.

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.