BIZTRAC BETA
Retail sale of automotive fuel

SKJÆRHUE AS

Org. no. 990698686 Limited company (AS) Risør Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −15,000
Equity NOK −220,000
Incorporated 2006
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−220k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SKJÆRHUE AS is registered as a limited company in Risør, Agder with organisation number 990698686. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drift av restaurant og dertil lignende aktiviteter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK −220,000

Financial health · 2024

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

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

Who owns SKJÆRHUE AS?

NEERGAARD EIENDOM AS
SKJÆRHUE AS
NOK 0 rev. · NOK −15,000 profit

SKJÆRHUE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SKJÆRHUE AS er morselskap for 1 datterselskap:

Frequently asked questions about SKJÆRHUE AS

Who owns SKJÆRHUE AS?

NEERGAARD EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SKJÆRHUE AS?

SKJÆRHUE AS had revenue of NOK 0 in 2024.

Where is SKJÆRHUE AS based?

SKJÆRHUE AS has its business address in Risør.

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

Report a problem

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