BIZTRAC BETA
Civil engineering activities

PRO-SPEC AS

Org. no. 924586982 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 277,000
Operating profit NOK 12,000
Equity NOK 22,000
Incorporated 2019
Share capital NOK 30,000

PRO-SPEC AS is registered as a limited company in Oslo, Oslo with organisation number 924586982. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å drive salg av tjenester knyttet til bygg og anlegg, kjøp og salg av eiendom, og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende 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 2025 financial year, show NOK 277,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 277,000
Operating profit
NOK 12,000
Equity
NOK 22,000
Est. value
NOK 73,000

Financial health · 2024

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.4%
Weak
Equity as a share of total capital

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

Who owns PRO-SPEC AS?

JOHN JOHANSEN
PRO-SPEC AS
NOK 277,000 rev. · NOK 12,000 profit

PRO-SPEC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PRO-SPEC AS

Who owns PRO-SPEC AS?

JOHN JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of PRO-SPEC AS?

PRO-SPEC AS had revenue of NOK 277,000 in 2025.

Who is the general manager of PRO-SPEC AS?

John Johansen is registered as general manager of PRO-SPEC AS.

Where is PRO-SPEC AS based?

PRO-SPEC 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.