BIZTRAC BETA
Activities of housing cooperatives

TJENESTEMANNSBOLIGLAGET FOR HORDALAND AS

Org. no. 930950262 Limited company (AS) Bergen Incorporated 1952 Active
Ownership graph ↗
Revenue 2024 NOK 912,000
Operating profit NOK 360,000
Equity NOK −3.4m
Incorporated 1952
Share capital NOK 101,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,4 mill kr).

TJENESTEMANNSBOLIGLAGET FOR HORDALAND AS is registered as a limited company in Bergen, Vestland with organisation number 930950262. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1952. Registered share capital is NOK 101,000, divided into 14 shares. The company's stated purpose is: “Drift av bolighus for sine aksjonærer på festet tomt - Kristofer Jansonsvei 27/29, Bergen.”. The most recent filed accounts, for the 2024 financial year, show NOK 912,000 in revenue and NOK 360,000 in operating profit.

Key figures · 2024

Revenue
NOK 912,000
Operating profit
NOK 360,000
Equity
NOK −3.4m
Est. value
NOK 1.4m

Financial health · 2024

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

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

Who owns TJENESTEMANNSBOLIGLAGET FOR HORDALAND AS?

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

Frequently asked questions about TJENESTEMANNSBOLIGLAGET FOR HORDALAND AS

What is the revenue of TJENESTEMANNSBOLIGLAGET FOR HORDALAND AS?

TJENESTEMANNSBOLIGLAGET FOR HORDALAND AS had revenue of NOK 912,000 in 2024.

Where is TJENESTEMANNSBOLIGLAGET FOR HORDALAND AS based?

TJENESTEMANNSBOLIGLAGET FOR HORDALAND 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 15.06.2026.

Report a problem

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