BIZTRAC BETA
Construction of residential and non-residential buildings

WOPEKX AS

Org. no. 992229942 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 534,000
Equity NOK 214,000
Incorporated 2008
Employees 5
Share capital NOK 100,000

WOPEKX AS is registered as a limited company in Oslo, Oslo with organisation number 992229942. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bygg og anlegg og andre aktiviteter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignede virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 534,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 534,000
Equity
NOK 214,000
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.9%
Good
Equity as a share of total capital

Who owns WOPEKX AS?

WOJCIECH STANISLAW KULESZA
WOPEKX AS
NOK 4.6m rev. · NOK 534,000 profit

WOPEKX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WOPEKX AS

Who owns WOPEKX AS?

WOJCIECH STANISLAW KULESZA is the largest registered owner, with 100.0%.

What is the revenue of WOPEKX AS?

WOPEKX AS had revenue of NOK 4.6m in 2024.

Who is the general manager of WOPEKX AS?

Wojciech Stanislaw Kulesza is registered as general manager of WOPEKX AS.

Where is WOPEKX AS based?

WOPEKX 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.