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

KARENBAKKEN BOLIGLAG AS

Org. no. 930483443 Limited company (AS) Bergen Incorporated 1946 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 1.3m
Equity NOK −10.9m
Incorporated 1946
Share capital NOK 110,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−10,9 mill kr).

KARENBAKKEN BOLIGLAG AS is registered as a limited company in Bergen, Vestland with organisation number 930483443. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1946. Registered share capital is NOK 110,000, divided into 2195 shares. The company's stated purpose is: “Å skaffe aksjeeierne bruksrett til egen bolig i selskapets eiendom (borett) og å drive virksomhet som står i sammenheng med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
▲ +14 %
Operating profit
NOK 1.3m
▲ +35 %
Equity
NOK −10.9m
▲ +5 %
Est. value
NOK 1.5m

Financial health · 2025

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

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

Who owns KARENBAKKEN BOLIGLAG AS?

No shareholders are registered for KARENBAKKEN BOLIGLAG AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about KARENBAKKEN BOLIGLAG AS

What is the revenue of KARENBAKKEN BOLIGLAG AS?

KARENBAKKEN BOLIGLAG AS had revenue of NOK 2.3m in 2025.

Where is KARENBAKKEN BOLIGLAG AS based?

KARENBAKKEN BOLIGLAG 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.