BIZTRAC BETA
Activities of excursion and event organisers

BILLETTO AS

Org. no. 996155064 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK −172,000
Equity NOK 220,000
Incorporated 2010
Share capital NOK 200,000

Signals

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

BILLETTO AS is registered as a limited company in Oslo, Oslo with organisation number 996155064. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2010. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Yte tjenester innenfor billetthåndtering, samt alt som står i forbindelse hermed, herunder deltagelse i selskaper med lignende eller annen virksomhet. Selskapet skal også delta i aksjemarkedet med overskuddslikviditet, og drive med kjøp og salg av fast eiendom, herunder deltagelse i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK −172,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
Operating profit
NOK −172,000
Equity
NOK 220,000
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.2%
Weak
Equity as a share of total capital

Who owns BILLETTO AS?

BILLETTO APS
BILLETTO AS
NOK 5.5m rev. · NOK −172,000 profit

BILLETTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILLETTO AS

Who owns BILLETTO AS?

BILLETTO APS is the largest registered owner, with 100.0%.

What is the revenue of BILLETTO AS?

BILLETTO AS had revenue of NOK 5.5m in 2025.

Where is BILLETTO AS based?

BILLETTO 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.