BIZTRAC BETA
Civil engineering activities

TUKI INVEST AS

Org. no. 933967484 Limited company (AS) Moss Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 117,000
Incorporated 2024
Share capital NOK 100,000

Signals

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

TUKI INVEST AS is registered as a limited company in Moss, Østfold with organisation number 933967484. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Erverv og forvaltning av aksjer og eierandeler i andre foretak og andre nærstående aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 117,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns TUKI INVEST AS?

STIAN ØSTLING
TUKI INVEST AS
NOK 0 rev. · NOK −8,000 profit

TUKI INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TUKI INVEST AS own?

TUKI INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TUKI INVEST AS

Who owns TUKI INVEST AS?

STIAN ØSTLING is the largest registered owner, with 100.0%.

What is the revenue of TUKI INVEST AS?

TUKI INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of TUKI INVEST AS?

Stian Østling is registered as general manager of TUKI INVEST AS.

Where is TUKI INVEST AS based?

TUKI INVEST AS has its business address in Moss.

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.