BIZTRAC BETA
Repair and maintenance of motor vehicles

ØLEN BILVASK AS

Org. no. 934140729 Limited company (AS) Haugesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 37,000
Operating profit NOK 4,000
Equity NOK 58,000
Incorporated 2024
Share capital NOK 30,000

ØLEN BILVASK AS is registered as a limited company in Haugesund, Rogaland with organisation number 934140729. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen bilvask - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 37,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2024

Revenue
NOK 37,000
Operating profit
NOK 4,000
Equity
NOK 58,000
Est. value
NOK 47,000

Financial health · 2024

Liquidity
1.91
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
47.8%
Weak
Equity as a share of total capital

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

Who owns ØLEN BILVASK AS?

MERETHE DANIELSEN BIRK
ØLEN BILVASK AS
NOK 37,000 rev. · NOK 4,000 profit

ØLEN BILVASK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØLEN BILVASK AS

Who owns ØLEN BILVASK AS?

MERETHE DANIELSEN BIRK is the largest registered owner, with 50.0%.

What is the revenue of ØLEN BILVASK AS?

ØLEN BILVASK AS had revenue of NOK 37,000 in 2024.

Who is the general manager of ØLEN BILVASK AS?

Trond Karsten Birk is registered as general manager of ØLEN BILVASK AS.

Where is ØLEN BILVASK AS based?

ØLEN BILVASK AS has its business address in Haugesund.

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.