biztrac. BETA
COMPANY REGISTER PROFILE
911932806 ORG. NO. 2022 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠HAUKELI STEIN DA is registered as “In liquidation” with the Brønnøysund Register Centre.
Quarrying of ornamental stone, limestone, gypsum, slate and other stone

HAUKELI STEIN DA

Org. no. 911932806 General partnership with shared liability (DA) Vinje Incorporated 2013 In liquidation
Ownership graph ↗
Revenue 2022 NOK 0
Operating profit NOK 0
Equity NOK 0
Incorporated 2013

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

HAUKELI STEIN DA is registered as a general partnership with shared liability in Vinje, Telemark with organisation number 911932806. The business is classified under quarrying of ornamental stone, limestone, gypsum, slate and other stone (NACE 08.110). The company was incorporated in 2013. The company's stated purpose is: “Framstilling og salg av knusa masser og andre produkt som naturleg fell saman med dette, herunder å delta i andre selskap med liknande verksemd.”. The most recent filed accounts, for the 2022 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2022

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 0

Financial health · 2022

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns HAUKELI STEIN DA?

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

Frequently asked questions about HAUKELI STEIN DA

What is the revenue of HAUKELI STEIN DA?

HAUKELI STEIN DA had revenue of NOK 0 in 2022.

Where is HAUKELI STEIN DA based?

HAUKELI STEIN DA has its business address in Edland.

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.