BIZTRAC BETA
Rental and operating of own or leased real estate

AKTIV FERIE AS

Org. no. 983079539 Limited company (AS) Østre Toten Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 242
Incorporated 2001
Share capital NOK 190,000

Signals

1 flags
  • Nylig endring 2026-07-24 Adresseendring registrert 2026-07-24.

AKTIV FERIE AS is registered as a limited company in Østre Toten, Innlandet with organisation number 983079539. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 190,000, divided into 1900 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendommer og annen virksomhet forbundet med dette herunder kjøp og salg av aksjer og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 242
Est. value
NOK 221

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
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 AKTIV FERIE AS?

ARTO INVEST AS
AKTIV FERIE AS
NOK 0 rev. · NOK 0 profit

AKTIV FERIE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AKTIV FERIE AS

Who owns AKTIV FERIE AS?

ARTO INVEST AS is the largest registered owner, with 33.4%.

What is the revenue of AKTIV FERIE AS?

AKTIV FERIE AS had revenue of NOK 0 in 2025.

Who is the general manager of AKTIV FERIE AS?

Arve Morten Granum is registered as general manager of AKTIV FERIE AS.

Where is AKTIV FERIE AS based?

AKTIV FERIE AS has its business address in Skreia.

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.