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

LIADALTERRASSEN BOLIGSAMEIE

Org. no. 982338530 Condominium flat owner (ESEK) Oslo Incorporated 1980 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 724,000
Equity NOK −6.7m
Incorporated 1980

Signals

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

LIADALTERRASSEN BOLIGSAMEIE is registered as a condominium flat owner in Oslo, Oslo with organisation number 982338530. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1980. The company's stated purpose is: “Sikre felles interesser og administrasjon av de i sameiet bestående eierseksjoner samt fellesarealer som sameierne gis bruksrett til.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 724,000 in operating profit.

Former names: BOLIGSAMEIET HERREGÅRDSVEIEN 2 A

Key figures · 2025

Revenue
NOK 2.4m
▲ +12 %
Operating profit
NOK 724,000
▲ +105 %
Equity
NOK −6.7m
▲ +3 %
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
8.50
Very good
Current assets ÷ current liabilities
Profitability
90.4%
Very good
Return on total assets
Solidity
-724.1%
Weak
Equity as a share of total capital

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

Who owns LIADALTERRASSEN BOLIGSAMEIE?

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

Frequently asked questions about LIADALTERRASSEN BOLIGSAMEIE

What is the revenue of LIADALTERRASSEN BOLIGSAMEIE?

LIADALTERRASSEN BOLIGSAMEIE had revenue of NOK 2.4m in 2025.

Where is LIADALTERRASSEN BOLIGSAMEIE based?

LIADALTERRASSEN BOLIGSAMEIE has its business address in Oslo.

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.