BIZTRAC BETA
COMPANY REGISTER PROFILE
813295342 ORG. NO. 2021 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

EIERSEKSJONSSAMEIET SANDERSTØLEN 60 NORD

Org. no. 813295342 Condominium flat owner (ESEK) Nord-Aurdal Incorporated 2014 Active
Ownership graph ↗
Revenue 2021 NOK 4.5m
Operating profit NOK −477,000
Equity NOK −86,000
Incorporated 2014

Signals

2 flags
  • Negativ egenkapital 2021 Bokført egenkapital er negativ (−86k kr).
  • Driftsunderskudd 2021 Siste driftsresultat er negativt (−477k kr).

EIERSEKSJONSSAMEIET SANDERSTØLEN 60 NORD is registered as a condominium flat owner in Nord-Aurdal, Innlandet with organisation number 813295342. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2014. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2021 financial year, show NOK 4.5m in revenue and NOK −477,000 in operating profit.

Key figures · 2021

Revenue
NOK 4.5m
Operating profit
NOK −477,000
Equity
NOK −86,000

Financial health · 2021

Liquidity
0.81
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.5%
Weak
Equity as a share of total capital

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

Who owns EIERSEKSJONSSAMEIET SANDERSTØLEN 60 NORD?

No shareholders are registered for EIERSEKSJONSSAMEIET SANDERSTØLEN 60 NORD in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about EIERSEKSJONSSAMEIET SANDERSTØLEN 60 NORD

What is the revenue of EIERSEKSJONSSAMEIET SANDERSTØLEN 60 NORD?

EIERSEKSJONSSAMEIET SANDERSTØLEN 60 NORD had revenue of NOK 4.5m in 2021.

Where is EIERSEKSJONSSAMEIET SANDERSTØLEN 60 NORD based?

EIERSEKSJONSSAMEIET SANDERSTØLEN 60 NORD has its business address in Tisleidalen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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