BIZTRAC BETA
Development of building projects

GME EIENDOM AS

Org. no. 919695455 Limited company (AS) Sarpsborg Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5,000
Equity NOK 1.3m
Incorporated 2017
Share capital NOK 1.6m

Signals

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

GME EIENDOM AS is registered as a limited company in Sarpsborg, Østfold with organisation number 919695455. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 1.6m, divided into 300 shares. The company's stated purpose is: “Drift og utvikling av eiendom til næring- og boligformål i Sarpsborg og omegn.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 1.3m
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns GME EIENDOM AS?

MENTU AS
GME EIENDOM AS
NOK 0 rev. · NOK −5,000 profit

GME EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GME EIENDOM AS own?

GME EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GME EIENDOM AS

Who owns GME EIENDOM AS?

MENTU AS is the largest registered owner, with 100.0%.

What is the revenue of GME EIENDOM AS?

GME EIENDOM AS had revenue of NOK 0 in 2024.

Where is GME EIENDOM AS based?

GME EIENDOM AS has its business address in Borgenhaugen.

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.