BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

XPROCO AS

Org. no. 997260678 Limited company (AS) Fredrikstad Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −150,000
Equity NOK 2.4m
Incorporated 2011
Share capital NOK 1.9m

Signals

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

XPROCO AS is registered as a limited company in Fredrikstad, Østfold with organisation number 997260678. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2011. Registered share capital is NOK 1.9m, divided into 116 shares. The company's stated purpose is: “Kjøp, salg, utleie og forvaltning av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −150,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −150,000
Equity
NOK 2.4m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns XPROCO AS?

RUNE KILEBU AS
XPROCO AS
NOK 1.2m rev. · NOK −150,000 profit

XPROCO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does XPROCO AS own?

XPROCO AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about XPROCO AS

Who owns XPROCO AS?

RUNE KILEBU AS is the largest registered owner, with 78.4%.

What is the revenue of XPROCO AS?

XPROCO AS had revenue of NOK 1.2m in 2024.

Where is XPROCO AS based?

XPROCO AS has its business address in Manstad.

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.