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

WELHAVENSGATE BOLIGLAG AS

Org. no. 930595489 Limited company (AS) Bergen Incorporated 1959 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 747,000
Equity NOK −1.9m
Incorporated 1959
Share capital NOK 100,000

Signals

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

WELHAVENSGATE BOLIGLAG AS is registered as a limited company in Bergen, Vestland with organisation number 930595489. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1959. Registered share capital is NOK 100,000, divided into 508 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 1.3m in revenue and NOK 747,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▼ −5 %
Operating profit
NOK 747,000
▼ −16 %
Equity
NOK −1.9m
▲ +23 %
Est. value
NOK 4.0m

Financial health · 2025

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

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

Who owns WELHAVENSGATE BOLIGLAG AS?

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

Frequently asked questions about WELHAVENSGATE BOLIGLAG AS

What is the revenue of WELHAVENSGATE BOLIGLAG AS?

WELHAVENSGATE BOLIGLAG AS had revenue of NOK 1.3m in 2025.

Where is WELHAVENSGATE BOLIGLAG AS based?

WELHAVENSGATE 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.