BIZTRAC BETA
Other tour operator activities

BIDWINTRAVEL.COM AS

Org. no. 998302935 Limited company (AS) Kongsvinger Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −76,000
Equity NOK −107,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−107k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−76k kr).

BIDWINTRAVEL.COM AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 998302935. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tjenesteyting og konsulentvirksomhet, og andre tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2024

Operating profit
NOK −76,000
Equity
NOK −107,000

Financial health · 2024

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-668.7%
Weak
Equity as a share of total capital

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

Who owns BIDWINTRAVEL.COM AS?

KONGSVINGER BUDGET HOTEL AS
BIDWINTRAVEL.COM AS
· NOK −76,000 profit

BIDWINTRAVEL.COM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIDWINTRAVEL.COM AS

Who owns BIDWINTRAVEL.COM AS?

KONGSVINGER BUDGET HOTEL AS is the largest registered owner, with 100.0%.

Who is the general manager of BIDWINTRAVEL.COM AS?

Hans Jørgen Reinhold Carlström is registered as general manager of BIDWINTRAVEL.COM AS.

Where is BIDWINTRAVEL.COM AS based?

BIDWINTRAVEL.COM AS has its business address in Kongsvinger.

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.