BIZTRAC BETA
Business and other management consultancy activities

INDUSTRIUKA EXPO AS

Org. no. 930265837 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 5.8m
Operating profit NOK 114,000
Equity NOK 938,000
Incorporated 2022
Share capital NOK 30,000

INDUSTRIUKA EXPO AS is registered as a limited company in Stavanger, Rogaland with organisation number 930265837. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i eiendom, konsulentvirksomhet, bedriftsutvikling og annet som naturlig faller sammen med dette, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.8m in revenue and NOK 114,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.8m
Operating profit
NOK 114,000
Equity
NOK 938,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns INDUSTRIUKA EXPO AS?

STAVANGER VEKST AS
INDUSTRIUKA EXPO AS
NOK 5.8m rev. · NOK 114,000 profit

INDUSTRIUKA EXPO AS has 3 registered shareholders:

All shareholders and roles →

Which companies does INDUSTRIUKA EXPO AS own?

INDUSTRIUKA EXPO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INDUSTRIUKA EXPO AS

Who owns INDUSTRIUKA EXPO AS?

STAVANGER VEKST AS is the largest registered owner, with 33.3%.

What is the revenue of INDUSTRIUKA EXPO AS?

INDUSTRIUKA EXPO AS had revenue of NOK 5.8m in 2024.

Where is INDUSTRIUKA EXPO AS based?

INDUSTRIUKA EXPO AS has its business address in Stavanger.

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.