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

SØNDRE ERLEVEIEN BOLIGLAG AS

Org. no. 930558931 Limited company (AS) Bergen Incorporated 1956 Active
Revenue 2025 NOK 3.9m
Operating profit NOK −7.4m
Equity NOK −14.5m
Incorporated 1956
Share capital NOK 101,000

Signals

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

SØNDRE ERLEVEIEN BOLIGLAG AS is registered as a limited company in Bergen, Vestland with organisation number 930558931. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1956. Registered share capital is NOK 101,000, divided into 5074 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 3.9m in revenue and NOK −7.4m in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
▲ +7 %
Operating profit
NOK −7.4m
▲ +2 %
Equity
NOK −14.5m
▼ −126 %

Financial health · 2025

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

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

Who owns SØNDRE ERLEVEIEN BOLIGLAG AS?

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

Frequently asked questions about SØNDRE ERLEVEIEN BOLIGLAG AS

What is the revenue of SØNDRE ERLEVEIEN BOLIGLAG AS?

SØNDRE ERLEVEIEN BOLIGLAG AS had revenue of NOK 3.9m in 2025.

Where is SØNDRE ERLEVEIEN BOLIGLAG AS based?

SØNDRE ERLEVEIEN 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.