BIZTRAC BETA
Computer programming activities

FTICKET AS

Org. no. 926173766 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 60,000
Incorporated 2020
Share capital NOK 200,000

Signals

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

FTICKET AS is registered as a limited company in Trondheim, Trøndelag with organisation number 926173766. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Utvikling av billettsystem, administrasjon og salg av billetter for kunder, samt hva som naturlig står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 60,000
Est. value
NOK 109,000

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 FTICKET AS?

TRONDHEIM SYSTEMUTVIKLING AS
FTICKET AS
NOK 0 rev. · NOK −17,000 profit

FTICKET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FTICKET AS

Who owns FTICKET AS?

TRONDHEIM SYSTEMUTVIKLING AS is the largest registered owner, with 50.0%.

What is the revenue of FTICKET AS?

FTICKET AS had revenue of NOK 0 in 2025.

Who is the general manager of FTICKET AS?

Trond Hillestad is registered as general manager of FTICKET AS.

Where is FTICKET AS based?

FTICKET AS has its business address in Trondheim.

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.