BIZTRAC BETA
Other captive investment companies

STIV KULING INVEST AS

Org. no. 928725405 Limited company (AS) Nordkapp Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 754,000
Incorporated 2022
Share capital NOK 820,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

STIV KULING INVEST AS is registered as a limited company in Nordkapp, Finnmark with organisation number 928725405. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2022. Registered share capital is NOK 820,000, divided into 820 shares. The company's stated purpose is: “Investering i aksjer og øvrige verdipapirer samt eiendom og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 754,000
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns STIV KULING INVEST AS?

FREDRIK TVEIT
STIV KULING INVEST AS
NOK 0 rev. · NOK −6,000 profit

STIV KULING INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does STIV KULING INVEST AS own?

STIV KULING INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STIV KULING INVEST AS

Who owns STIV KULING INVEST AS?

FREDRIK TVEIT is the largest registered owner, with 25.0%.

What is the revenue of STIV KULING INVEST AS?

STIV KULING INVEST AS had revenue of NOK 0 in 2025.

Where is STIV KULING INVEST AS based?

STIV KULING INVEST AS has its business address in Honningsvåg.

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.