biztrac. BETA
COMPANY REGISTER PROFILE
929120302 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Geological surveying

PXGEO NORWAY AS

Org. no. 929120302 Limited company (AS) Oslo Incorporated 2022 Active
Revenue 2025 NOK 1.1bn
Operating profit NOK 13.8m
Equity NOK 22.6m
Incorporated 2022
Share capital NOK 465,000

PXGEO NORWAY AS is registered as a limited company in Oslo, Oslo with organisation number 929120302. The business is classified under geological surveying (NACE 71.122). The company was incorporated in 2022. Registered share capital is NOK 465,000, divided into 465039 shares. The company's stated purpose is: “Utvikling av geofysiske utstyr og metoder, genering, markedsføring og salg av eksklusive og ikke-eksklusive geofysiske undersøkelser samt annen virksomhet som faller inn under dette, herunder investering i slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1bn in revenue and NOK 13.8m in operating profit.

Former names: AMPSEIS AS

Key figures · 2025

Revenue
NOK 1.1bn
▲ +54608 %
Operating profit
NOK 13.8m
▲ +1209 %
Equity
NOK 22.6m
▲ +81 %
Est. value
NOK 105.3m

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
11.2%
Satisfactory
Equity as a share of total capital

Who owns PXGEO NORWAY AS?

MANTA SYSTEMS LIMITED KY
PXGEO NORWAY AS
NOK 1.1bn rev. · NOK 13.8m profit

PXGEO NORWAY AS has 1 registered shareholder:

  • MANTA SYSTEMS LIMITED 100.0%
All shareholders and roles →

Frequently asked questions about PXGEO NORWAY AS

Who owns PXGEO NORWAY AS?

MANTA SYSTEMS LIMITED is the largest registered owner, with 100.0%.

What is the revenue of PXGEO NORWAY AS?

PXGEO NORWAY AS had revenue of NOK 1.1bn in 2025.

Where is PXGEO NORWAY AS based?

PXGEO NORWAY 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.