BIZTRAC BETA
Uoppgitt

HOLSKOG INVEST AS

Org. no. 919054670 Limited company (AS) Kristiansand Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −392,000
Equity NOK 44.6m
Incorporated 2017
Share capital NOK 40,000

Signals

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

HOLSKOG INVEST AS is registered as a limited company in Kristiansand, Agder with organisation number 919054670. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 40,000, divided into 80000 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer og andeler i selskap etter selskapsloven, obligasjoner, fast eiendom, 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 −392,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −392,000
Equity
NOK 44.6m
Est. value
NOK 103.0m

Financial health · 2025

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

Who owns HOLSKOG INVEST AS?

TERJE HOLSKOG
HOLSKOG INVEST AS
NOK 0 rev. · NOK −392,000 profit

HOLSKOG INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HOLSKOG INVEST AS own?

HOLSKOG INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HOLSKOG INVEST AS

Who owns HOLSKOG INVEST AS?

TERJE HOLSKOG is the largest registered owner, with 90.0%.

What is the revenue of HOLSKOG INVEST AS?

HOLSKOG INVEST AS had revenue of NOK 0 in 2024.

Where is HOLSKOG INVEST AS based?

HOLSKOG INVEST AS has its business address in Kristiansand S.

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.