biztrac. BETA
COMPANY REGISTER PROFILE
922150346 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Travel agency activities

VANDRING PÅ BALKAN AS

Org. no. 922150346 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 162,000
Operating profit NOK −8,000
Equity NOK 61,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

VANDRING PÅ BALKAN AS is registered as a limited company in Oslo, Oslo with organisation number 922150346. The business is classified under travel agency activities (NACE 79.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Reisebyrå.”. The most recent filed accounts, for the 2025 financial year, show NOK 162,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 162,000
▼ −52 %
Operating profit
NOK −8,000
▼ −163 %
Equity
NOK 61,000
▼ −21 %
Est. value
NOK 43,000

Financial health · 2025

Liquidity
267.54
Very good
Current assets ÷ current liabilities
Profitability
-1.7%
Not satisfactory
Return on total assets
Solidity
99.6%
Weak
Equity as a share of total capital

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

Who owns VANDRING PÅ BALKAN AS?

MAJA TRAJKOVSKA GB
VANDRING PÅ BALKAN AS
NOK 162,000 rev. · NOK −8,000 profit

VANDRING PÅ BALKAN AS has 2 registered shareholders:

  • DEBI AS 50.0%
  • MAJA TRAJKOVSKA 50.0%
All shareholders and roles →

Frequently asked questions about VANDRING PÅ BALKAN AS

Who owns VANDRING PÅ BALKAN AS?

DEBI AS is the largest registered owner, with 50.0%.

What is the revenue of VANDRING PÅ BALKAN AS?

VANDRING PÅ BALKAN AS had revenue of NOK 162,000 in 2025.

Where is VANDRING PÅ BALKAN AS based?

VANDRING PÅ BALKAN 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 03.10.2026.

Report a problem

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