BIZTRAC BETA
Operation of car parks and garages

OSESTØLEN BILSTALL AS

Org. no. 994293001 Limited company (AS) Hol Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 321,000
Operating profit NOK −173,000
Equity NOK −3.4m
Incorporated 2009
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,4 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−173k kr).

OSESTØLEN BILSTALL AS is registered as a limited company in Hol, Buskerud with organisation number 994293001. The business is classified under operation of car parks and garages (NACE 52.212). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 52 shares. The company's stated purpose is: “Drift av parkeringsbygg, og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 321,000 in revenue and NOK −173,000 in operating profit.

Key figures · 2025

Revenue
NOK 321,000
Operating profit
NOK −173,000
Equity
NOK −3.4m

Financial health · 2025

Liquidity
21.47
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-50.1%
Weak
Equity as a share of total capital

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

Who owns OSESTØLEN BILSTALL AS?

STOREBRANDS FOND FOR ANSATTE STI
OSESTØLEN BILSTALL AS
NOK 321,000 rev. · NOK −173,000 profit

OSESTØLEN BILSTALL AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about OSESTØLEN BILSTALL AS

Who owns OSESTØLEN BILSTALL AS?

STOREBRANDS FOND FOR ANSATTE STI is the largest registered owner, with 3.8%.

What is the revenue of OSESTØLEN BILSTALL AS?

OSESTØLEN BILSTALL AS had revenue of NOK 321,000 in 2025.

Where is OSESTØLEN BILSTALL AS based?

OSESTØLEN BILSTALL AS has its business address in Ustaoset.

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.