BIZTRAC BETA
Construction of residential and non-residential buildings

PROCUREMENT AS

Org. no. 922160198 Limited company (AS) Indre Østfold Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −45,000
Equity NOK 3.1m
Incorporated 2019
Share capital NOK 60,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−45k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PROCUREMENT AS is registered as a limited company in Indre Østfold, Østfold with organisation number 922160198. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 2 shares. The company's stated purpose is: “Investeringer i børsnoterte aksjer og aksjefond, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −45,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −45,000
Equity
NOK 3.1m
Est. value
NOK 6.4m

Financial health · 2024

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

Who owns PROCUREMENT AS?

PKR HOLDINGS AS
PROCUREMENT AS
NOK 0 rev. · NOK −45,000 profit

PROCUREMENT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

PROCUREMENT AS er morselskap for 7 datterselskaper:

Frequently asked questions about PROCUREMENT AS

Who owns PROCUREMENT AS?

PKR HOLDINGS AS is the largest registered owner, with 100.0%.

What is the revenue of PROCUREMENT AS?

PROCUREMENT AS had revenue of NOK 0 in 2024.

Where is PROCUREMENT AS based?

PROCUREMENT AS has its business address in Trøgstad.

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.