BIZTRAC BETA
COMPANY REGISTER PROFILE
932220679 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Sewerage

LYKKJA AVLØPSANLEGG SA

Org. no. 932220679 Co-operation (SA) Hemsedal Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −4.0m
Equity NOK −8.3m
Incorporated 2023

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−8,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4,0 mill kr).

LYKKJA AVLØPSANLEGG SA is registered as a co-operation in Hemsedal, Buskerud with organisation number 932220679. The business is classified under sewerage (NACE 37.000). The company was incorporated in 2023. The company's stated purpose is: “Etablere et avløpsanlegg i området Lykkja i Hemsedal.”.

Key figures · 2025

Operating profit
NOK −4.0m
Equity
NOK −8.3m

Financial health · 2025

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

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

Who owns LYKKJA AVLØPSANLEGG SA?

No shareholders are registered for LYKKJA AVLØPSANLEGG SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LYKKJA AVLØPSANLEGG SA

Where is LYKKJA AVLØPSANLEGG SA based?

LYKKJA AVLØPSANLEGG SA has its business address in Hemsedal.

Property

Business address c/o Impruv Accounting AS Lykkjavegen 659, 3560 Hemsedal
Cadastral unit 3326-52/3/0/0
Building Våningshus · 1 unit

5 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.