BIZTRAC BETA
Retail sale of other food

EROBRA EIENDOM AS

Org. no. 985771944 Limited company (AS) Melhus Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 77,000
Operating profit NOK −354,000
Equity NOK −4.8m
Incorporated 2003
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,8 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−354k kr).

EROBRA EIENDOM AS is registered as a limited company in Melhus, Trøndelag with organisation number 985771944. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å investere i eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 77,000 in revenue and NOK −354,000 in operating profit.

Key figures · 2025

Revenue
NOK 77,000
Operating profit
NOK −354,000
Equity
NOK −4.8m

Financial health · 2024

Liquidity
35.00
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-50.4%
Weak
Equity as a share of total capital

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

Who owns EROBRA EIENDOM AS?

RUNE OTERHOLM
EROBRA EIENDOM AS
NOK 77,000 rev. · NOK −354,000 profit

EROBRA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EROBRA EIENDOM AS own?

EROBRA EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about EROBRA EIENDOM AS

Who owns EROBRA EIENDOM AS?

RUNE OTERHOLM is the largest registered owner, with 100.0%.

What is the revenue of EROBRA EIENDOM AS?

EROBRA EIENDOM AS had revenue of NOK 77,000 in 2025.

Where is EROBRA EIENDOM AS based?

EROBRA EIENDOM AS has its business address in Melhus.

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.