biztrac. BETA
COMPANY REGISTER PROFILE
830787682 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

2BR EIENDOM AS

Org. no. 830787682 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 1.2m
Equity NOK −725,000
Incorporated 2023
Share capital NOK 60,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−725k kr).

2BR EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 830787682. 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 60,000, divided into 60000 shares. The company's stated purpose is: “Investeringsvirksomhet i finansaktiva samt kjøp, salg, utvikling og utbygging av fast eiendom og alt som faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 1.2m
▲ +933 %
Equity
NOK −725,000
▲ +50 %
Est. value
NOK 6.1m

Financial health · 2025

Liquidity
125.42
Very good
Current assets ÷ current liabilities
Profitability
11.6%
Good
Return on total assets
Solidity
-17.6%
Weak
Equity as a share of total capital

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

Who owns 2BR EIENDOM AS?

2BR EIENDOM AS
NOK 1.6m rev. · NOK 1.2m profit

2BR EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about 2BR EIENDOM AS

Who owns 2BR EIENDOM AS?

NYE ROYAL EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of 2BR EIENDOM AS?

2BR EIENDOM AS had revenue of NOK 1.6m in 2025.

Where is 2BR EIENDOM AS based?

2BR EIENDOM AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.