BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

O.B.WIIK INTERNATIONAL AS

Org. no. 932539284 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 30.9m
Operating profit NOK 6.4m
Equity NOK 10.2m
Incorporated 2023
Share capital NOK 1.0m

O.B.WIIK INTERNATIONAL AS is registered as a limited company in Lillestrøm, Akershus with organisation number 932539284. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2023. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Salg og utleie av haller til internasjonale kunder.”. The most recent filed accounts, for the 2024 financial year, show NOK 30.9m in revenue and NOK 6.4m in operating profit.

Key figures · 2024

Revenue
NOK 30.9m
Operating profit
NOK 6.4m
Equity
NOK 10.2m
Est. value
NOK 25.2m

Financial health · 2024

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.3%
Very good
Equity as a share of total capital

Who owns O.B.WIIK INTERNATIONAL AS?

ZURHAAR INDUSTRIES AS
O.B.WIIK INTERNATIONAL AS
NOK 30.9m rev. · NOK 6.4m profit

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

All shareholders and roles →

Frequently asked questions about O.B.WIIK INTERNATIONAL AS

Who owns O.B.WIIK INTERNATIONAL AS?

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

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

O.B.WIIK INTERNATIONAL AS had revenue of NOK 30.9m in 2024.

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

Ole Gregersen is registered as general manager of O.B.WIIK INTERNATIONAL AS.

Where is O.B.WIIK INTERNATIONAL AS based?

O.B.WIIK INTERNATIONAL 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.