BIZTRAC BETA
Uoppgitt

SKARDING INVEST AS

Org. no. 927626616 Limited company (AS) Porsgrunn Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −4,000
Equity NOK 2.5m
Incorporated 2021
Share capital NOK 38,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4k kr).

SKARDING INVEST AS is registered as a limited company in Porsgrunn, Telemark with organisation number 927626616. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 38,000, divided into 3846 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder deltakelse i andre selskaper, investeringer i aksjer, verdipapirer og andre formuesobjekter, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 2.5m
Est. value
NOK 3.0m

Financial health · 2024

Liquidity
9.20
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.8%
Very good
Equity as a share of total capital

Who owns SKARDING INVEST AS?

KIM GJØRAN SKARDING
SKARDING INVEST AS
NOK 0 rev. · NOK −4,000 profit

SKARDING INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKARDING INVEST AS own?

SKARDING INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKARDING INVEST AS

Who owns SKARDING INVEST AS?

KIM GJØRAN SKARDING is the largest registered owner, with 100.0%.

What is the revenue of SKARDING INVEST AS?

SKARDING INVEST AS had revenue of NOK 0 in 2024.

Where is SKARDING INVEST AS based?

SKARDING INVEST AS has its business address in Porsgrunn.

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.