BIZTRAC BETA
Computer programming activities

BIFROST BOOKING AS

Org. no. 824599742 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 142,000
Operating profit NOK −10,000
Equity NOK 245,000
Incorporated 2020
Share capital NOK 32,000

Signals

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

BIFROST BOOKING AS is registered as a limited company in Oslo, Oslo with organisation number 824599742. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 32,000, divided into 1053 shares. The company's stated purpose is: “Utvikle og drifte programvare for turistnæringen og tilby den beste løsningen til SMB markedet og eller beslektet dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 142,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 142,000
Operating profit
NOK −10,000
Equity
NOK 245,000
Est. value
NOK 350,000

Financial health · 2025

Liquidity
2.90
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.0%
Good
Equity as a share of total capital

Who owns BIFROST BOOKING AS?

ESPEN ANDRE EDVARDSEN
BIFROST BOOKING AS
NOK 142,000 rev. · NOK −10,000 profit

BIFROST BOOKING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIFROST BOOKING AS

Who owns BIFROST BOOKING AS?

ESPEN ANDRE EDVARDSEN is the largest registered owner, with 42.7%.

What is the revenue of BIFROST BOOKING AS?

BIFROST BOOKING AS had revenue of NOK 142,000 in 2025.

Who is the general manager of BIFROST BOOKING AS?

Patrick Harlem Skovrand is registered as general manager of BIFROST BOOKING AS.

Where is BIFROST BOOKING AS based?

BIFROST BOOKING 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.