BIZTRAC BETA
Residential care activities for persons living with or having a diagnosis of intellectual disability

BIDCO SPIRIT AS

Org. no. 827233072 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −493,000
Equity NOK 263.9m
Incorporated 2021
Share capital NOK 30.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−493k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BIDCO SPIRIT AS is registered as a limited company in Oslo, Oslo with organisation number 827233072. The business is classified under residential care activities for persons living with or having a diagnosis of intellectual disability (NACE 87.202). The company was incorporated in 2021. Registered share capital is NOK 30.0m, divided into 300000 shares. The company's stated purpose is: “Holdingselskap. Investeringer i aksjer og øvrige verdipapirer.”.

Key figures · 2024

Operating profit
NOK −493,000
Equity
NOK 263.9m
Est. value
NOK 409.1m

Financial health · 2024

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

Who owns BIDCO SPIRIT AS?

HOLDCO SPIRIT AS
BIDCO SPIRIT AS
· NOK −493,000 profit

BIDCO SPIRIT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BIDCO SPIRIT AS own?

BIDCO SPIRIT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BIDCO SPIRIT AS

Who owns BIDCO SPIRIT AS?

HOLDCO SPIRIT AS is the largest registered owner, with 100.0%.

Who is the general manager of BIDCO SPIRIT AS?

Per Gunnar Borhaug is registered as general manager of BIDCO SPIRIT AS.

Where is BIDCO SPIRIT AS based?

BIDCO SPIRIT 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.