BIZTRAC BETA
Civil engineering activities

PRO DOK 3D AS

Org. no. 924486961 Limited company (AS) Stavanger Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 12.3m
Operating profit NOK 951,000
Equity NOK −189,000
Incorporated 2020
Employees 11
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−189k kr).

PRO DOK 3D AS is registered as a limited company in Stavanger, Rogaland with organisation number 924486961. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2020 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester innen bygg og anlegg og alt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.3m in revenue and NOK 951,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.3m
Operating profit
NOK 951,000
Equity
NOK −189,000
Est. value
NOK 6.4m

Financial health · 2024

Liquidity
0.72
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.1%
Weak
Equity as a share of total capital

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

Who owns PRO DOK 3D AS?

PRO DOK HOLDING AS
PRO DOK 3D AS
NOK 12.3m rev. · NOK 951,000 profit

PRO DOK 3D AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PRO DOK 3D AS

Who owns PRO DOK 3D AS?

PRO DOK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PRO DOK 3D AS?

PRO DOK 3D AS had revenue of NOK 12.3m in 2024.

Who is the general manager of PRO DOK 3D AS?

Roy Kenneth Skretting is registered as general manager of PRO DOK 3D AS.

Where is PRO DOK 3D AS based?

PRO DOK 3D 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.