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

SAMEIET HUSBYKLEIVA TERRASSE

Org. no. 984903170 Condominium flat owner (ESEK) Stjørdal Incorporated 2001 Active
Revenue 2025 NOK 1.9m
Operating profit NOK −1.2m
Equity NOK −28,000
Incorporated 2001

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−28k kr).

SAMEIET HUSBYKLEIVA TERRASSE is registered as a condominium flat owner in Stjørdal, Trøndelag with organisation number 984903170. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2001. The company's stated purpose is: “Den enkelte enhet skal brukes til boligformål. Bruksenhetene kan ikke anvendes til næringsformål. Med næringsformål menes ethvert formål som ikke er boligformål.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −1.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▲ +17 %
Operating profit
NOK −1.2m
▼ −39757 %
Equity
NOK −28,000
▼ −102 %

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
-56.0%
Not satisfactory
Return on total assets
Solidity
-1.4%
Weak
Equity as a share of total capital

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

Who owns SAMEIET HUSBYKLEIVA TERRASSE?

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

Frequently asked questions about SAMEIET HUSBYKLEIVA TERRASSE

What is the revenue of SAMEIET HUSBYKLEIVA TERRASSE?

SAMEIET HUSBYKLEIVA TERRASSE had revenue of NOK 1.9m in 2025.

Where is SAMEIET HUSBYKLEIVA TERRASSE based?

SAMEIET HUSBYKLEIVA TERRASSE has its business address in Stjørdal.

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.