BIZTRAC BETA
Buying and selling of own real estate

BEMIO AS

Org. no. 923473424 Limited company (AS) Øvre Eiker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 5,000
Operating profit NOK −9,000
Equity NOK −37,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−37k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

BEMIO AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 923473424. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Aksjeinvesteringer, deltagelse i annen virksomhet, samt kjøp, salg og utleie av eiendom, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 5,000
Operating profit
NOK −9,000
Equity
NOK −37,000

Financial health · 2024

Liquidity
0.29
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-240.9%
Weak
Equity as a share of total capital

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

Who owns BEMIO AS?

BJØRN ERIK ARNESEN
BEMIO AS
NOK 5,000 rev. · NOK −9,000 profit

BEMIO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BEMIO AS

Who owns BEMIO AS?

BJØRN ERIK ARNESEN is the largest registered owner, with 50.0%.

What is the revenue of BEMIO AS?

BEMIO AS had revenue of NOK 5,000 in 2024.

Who is the general manager of BEMIO AS?

Bjørn Erik Arnesen is registered as general manager of BEMIO AS.

Where is BEMIO AS based?

BEMIO AS has its business address in Vestfossen.

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.