BIZTRAC BETA
Other specialised construction activities n.e.c.

O.B.WIIK SERVICES AS

Org. no. 932539241 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 79.2m
Operating profit NOK 5.0m
Equity NOK 5.1m
Incorporated 2023
Employees 14
Share capital NOK 1.0m

O.B.WIIK SERVICES AS is registered as a limited company in Lillestrøm, Akershus with organisation number 932539241. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2023 and has 14 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Utleie av arrangementsutstyr og salg av tjenester som hører til, montasje og servicearbeid innen bygg og anlegg.”. The most recent filed accounts, for the 2024 financial year, show NOK 79.2m in revenue and NOK 5.0m in operating profit.

Key figures · 2024

Revenue
NOK 79.2m
Operating profit
NOK 5.0m
Equity
NOK 5.1m
Est. value
NOK 18.9m

Financial health · 2024

Liquidity
0.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.0%
Satisfactory
Equity as a share of total capital

Who owns O.B.WIIK SERVICES AS?

ZURHAAR INDUSTRIES AS
O.B.WIIK SERVICES AS
NOK 79.2m rev. · NOK 5.0m profit

O.B.WIIK SERVICES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about O.B.WIIK SERVICES AS

Who owns O.B.WIIK SERVICES AS?

ZURHAAR INDUSTRIES AS is the largest registered owner, with 100.0%.

What is the revenue of O.B.WIIK SERVICES AS?

O.B.WIIK SERVICES AS had revenue of NOK 79.2m in 2024.

Who is the general manager of O.B.WIIK SERVICES AS?

Geir Aasen is registered as general manager of O.B.WIIK SERVICES AS.

Where is O.B.WIIK SERVICES AS based?

O.B.WIIK SERVICES AS has its business address in Skedsmokorset.

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.