biztrac. BETA
COMPANY REGISTER PROFILE
934200098 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

BORETTSLAGET MICHAEL KROHNS GATE 23

Org. no. 934200098 Housing cooperative (BRL) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 454,000
Operating profit NOK −35,000
Equity NOK −590,000
Incorporated 2024

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−590k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).

BORETTSLAGET MICHAEL KROHNS GATE 23 is registered as a housing cooperative in Bergen, Vestland with organisation number 934200098. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2024. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 454,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 454,000
▼ −66 %
Operating profit
NOK −35,000
▼ −107 %
Equity
NOK −590,000
▲ +18 %
Est. value
NOK 842,000

Financial health · 2025

Liquidity
28.04
Very good
Current assets ÷ current liabilities
Profitability
-0.1%
Not satisfactory
Return on total assets
Solidity
-2.7%
Weak
Equity as a share of total capital

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

Who owns BORETTSLAGET MICHAEL KROHNS GATE 23?

No shareholders are registered for BORETTSLAGET MICHAEL KROHNS GATE 23 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BORETTSLAGET MICHAEL KROHNS GATE 23

What is the revenue of BORETTSLAGET MICHAEL KROHNS GATE 23?

BORETTSLAGET MICHAEL KROHNS GATE 23 had revenue of NOK 454,000 in 2025.

Where is BORETTSLAGET MICHAEL KROHNS GATE 23 based?

BORETTSLAGET MICHAEL KROHNS GATE 23 has its business address in Hjellestad.

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.