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

EIERSEKSJONSSAMEIET SKOGRYGGVEIEN 1

Org. no. 992546182 Condominium flat owner (ESEK) Oslo Incorporated 2007 Active
Revenue 2023 NOK 374,000
Operating profit NOK −63,000
Equity NOK 553
Incorporated 2007

Signals

1 flags
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−63k kr).

EIERSEKSJONSSAMEIET SKOGRYGGVEIEN 1 is registered as a condominium flat owner in Oslo, Oslo with organisation number 992546182. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2007. The company's stated purpose is: “Å ivareta sameiernes fellesinteresser og administrasjon av eiendommen med fellesanlegg av enhver art.”. The most recent filed accounts, for the 2023 financial year, show NOK 374,000 in revenue and NOK −63,000 in operating profit.

Key figures · 2023

Revenue
NOK 374,000
▼ −8 %
Operating profit
NOK −63,000
▼ −75 %
Equity
NOK 553
▼ −99 %
Est. value
NOK 232,000

Financial health · 2023

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
-26.1%
Not satisfactory
Return on total assets
Solidity
0.3%
Weak
Equity as a share of total capital

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

Who owns EIERSEKSJONSSAMEIET SKOGRYGGVEIEN 1?

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

Frequently asked questions about EIERSEKSJONSSAMEIET SKOGRYGGVEIEN 1

What is the revenue of EIERSEKSJONSSAMEIET SKOGRYGGVEIEN 1?

EIERSEKSJONSSAMEIET SKOGRYGGVEIEN 1 had revenue of NOK 374,000 in 2023.

Where is EIERSEKSJONSSAMEIET SKOGRYGGVEIEN 1 based?

EIERSEKSJONSSAMEIET SKOGRYGGVEIEN 1 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.