biztrac. BETA
COMPANY REGISTER PROFILE
933351009 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

JANTU AS

Org. no. 933351009 Limited company (AS) Smøla Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 75,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

JANTU AS is registered as a limited company in Smøla, Møre og Romsdal with organisation number 933351009. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å utøve aktivitet som holdingselskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Former names: JATU AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
▼ −34 %
Equity
NOK 75,000
▼ −17 %
Est. value
NOK 88,000

Financial health · 2025

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

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

Who owns JANTU AS?

JANTU AS
NOK 0 rev. · NOK −15,000 profit

JANTU AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JANTU AS own?

JANTU AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JANTU AS

Who owns JANTU AS?

Jan Dagfinn Tuven is the largest registered owner, with 100.0%.

What is the revenue of JANTU AS?

JANTU AS had revenue of NOK 0 in 2025.

Who is the general manager of JANTU AS?

Jan Dagfinn Tuven is registered as general manager of JANTU AS.

Where is JANTU AS based?

JANTU AS has its business address in Smøla.

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

Report a problem

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