BIZTRAC BETA
Rental and operating of own or leased real estate

APALTUN HOLDING AS

Org. no. 926060732 Limited company (AS) Kvam Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −8,000
Equity NOK 15.9m
Incorporated 2020
Share capital NOK 80,000

Signals

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

APALTUN HOLDING AS is registered as a limited company in Kvam, Vestland with organisation number 926060732. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 80,000, divided into 30000 shares. The company's stated purpose is: “Investering og eierskap i og finansiering av andre selskaper, samt bistå med organisering og drift av slike selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 15.9m
Est. value
NOK 14.5m

Financial health · 2024

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

Who owns APALTUN HOLDING AS?

STIG MO
APALTUN HOLDING AS
NOK 0 rev. · NOK −8,000 profit

APALTUN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does APALTUN HOLDING AS own?

APALTUN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about APALTUN HOLDING AS

Who owns APALTUN HOLDING AS?

STIG MO is the largest registered owner, with 100.0%.

What is the revenue of APALTUN HOLDING AS?

APALTUN HOLDING AS had revenue of NOK 0 in 2024.

Where is APALTUN HOLDING AS based?

APALTUN HOLDING AS has its business address in Norheimsund.

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.