BIZTRAC BETA
Rental and operating of own or leased real estate

BRUÅSEN EIENDOM AS

Org. no. 932295539 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −14,000
Equity NOK 361,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−14k kr).

BRUÅSEN EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932295539. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie og drift av fast eiendom, samt deltakelse i andre selskaper som aksjeeier på en eller annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 361,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns BRUÅSEN EIENDOM AS?

KARI METTE ERRING
BRUÅSEN EIENDOM AS
NOK 0 rev. · NOK −14,000 profit

BRUÅSEN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BRUÅSEN EIENDOM AS own?

BRUÅSEN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRUÅSEN EIENDOM AS

Who owns BRUÅSEN EIENDOM AS?

KARI METTE ERRING is the largest registered owner, with 33.3%.

What is the revenue of BRUÅSEN EIENDOM AS?

BRUÅSEN EIENDOM AS had revenue of NOK 0 in 2024.

Where is BRUÅSEN EIENDOM AS based?

BRUÅSEN EIENDOM AS has its business address in Trondheim.

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.