BIZTRAC BETA
Other tour operator activities

BACKPACKER AS

Org. no. 925524646 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK −528,000
Equity NOK −1.8m
Incorporated 2020
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,8 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−528k kr).

BACKPACKER AS is registered as a limited company in Oslo, Oslo with organisation number 925524646. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Reisearrangørvirksomhet og det som naturlig faller innunder reisevirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK −528,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK −528,000
Equity
NOK −1.8m

Financial health · 2024

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

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

Who owns BACKPACKER AS?

LIEN GRUPPEN AS
BACKPACKER AS
NOK 1.8m rev. · NOK −528,000 profit

BACKPACKER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BACKPACKER AS

Who owns BACKPACKER AS?

LIEN GRUPPEN AS is the largest registered owner, with 75.0%.

What is the revenue of BACKPACKER AS?

BACKPACKER AS had revenue of NOK 1.8m in 2024.

Who is the general manager of BACKPACKER AS?

Kasper Heron Aulesjord is registered as general manager of BACKPACKER AS.

Where is BACKPACKER AS based?

BACKPACKER AS has its business address in Oslo.

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.