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

GXP PUBLISHING AS

Org. no. 913361857 Limited company (AS) Asker Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 303,000
Equity NOK 385,000
Incorporated 2014
Share capital NOK 100,000

GXP PUBLISHING AS is registered as a limited company in Asker, Akershus with organisation number 913361857. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Formidling, kommunikasjon og nettverksbygging innenfor geofagmiljøet og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 303,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 303,000
Equity
NOK 385,000
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns GXP PUBLISHING AS?

ICARSTENS INVEST AS
GXP PUBLISHING AS
NOK 4.2m rev. · NOK 303,000 profit

GXP PUBLISHING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GXP PUBLISHING AS

Who owns GXP PUBLISHING AS?

ICARSTENS INVEST AS is the largest registered owner, with 51.0%.

What is the revenue of GXP PUBLISHING AS?

GXP PUBLISHING AS had revenue of NOK 4.2m in 2024.

Where is GXP PUBLISHING AS based?

GXP PUBLISHING AS has its business address in Heggedal.

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.