biztrac. BETA
COMPANY REGISTER PROFILE
928882624 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

TRAVL AS

Org. no. 928882624 Limited company (AS) Horten Incorporated 2022 Active
Revenue 2025 NOK 2,000
Operating profit NOK −10,000
Equity NOK −40,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−40k kr).

TRAVL AS is registered as a limited company in Horten, Vestfold with organisation number 928882624. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “It tjenester, salg reisetjenester og utvikling av webløsninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 2,000 in revenue and NOK −10,000 in operating profit.

Former names: HORTEN BYGG & BETONG AS, VELORY AS

Key figures · 2025

Revenue
NOK 2,000
Operating profit
NOK −10,000
▲ +90 %
Equity
NOK −40,000
▼ −59 %

Financial health · 2025

Liquidity
-0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
-59.1%
Not satisfactory
Return on total assets
Solidity
-340.9%
Weak
Equity as a share of total capital

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

Who owns TRAVL AS?

TRAVL AS
NOK 2,000 rev. · NOK −10,000 profit

TRAVL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRAVL AS

Who owns TRAVL AS?

Jonas Østbye Gundersen is the largest registered owner, with 100.0%.

What is the revenue of TRAVL AS?

TRAVL AS had revenue of NOK 2,000 in 2025.

Who is the general manager of TRAVL AS?

Jonas Østbye Gundersen is registered as general manager of TRAVL AS.

Where is TRAVL AS based?

TRAVL AS has its business address in Horten.

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.