biztrac. BETA
COMPANY REGISTER PROFILE
934998634 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Hotels and similar accommodation

ÅBOTEN HOLDING AS

Org. no. 934998634 Limited company (AS) Frosta Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 3.2m
Incorporated 2025
Share capital NOK 70,000

Signals

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

ÅBOTEN HOLDING AS is registered as a limited company in Frosta, Trøndelag with organisation number 934998634. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2025. Registered share capital is NOK 70,000, divided into 100 shares. The company's stated purpose is: “Investere og eie aksjer i andre selskap, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 3.2m
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
3328.82
Very good
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 ÅBOTEN HOLDING AS?

ÅBOTEN HOLDING AS
NOK 0 rev. · NOK −2,000 profit

ÅBOTEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ÅBOTEN HOLDING AS own?

ÅBOTEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ÅBOTEN HOLDING AS

Who owns ÅBOTEN HOLDING AS?

Jørn Gunnarson Anderssen is the largest registered owner, with 100.0%.

What is the revenue of ÅBOTEN HOLDING AS?

ÅBOTEN HOLDING AS had revenue of NOK 0 in 2025.

Where is ÅBOTEN HOLDING AS based?

ÅBOTEN HOLDING AS has its business address in Frosta.

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.