BIZTRAC BETA
Manufacture of other technical and industrial textiles

GE-MO AS

Org. no. 929414357 Limited company (AS) Tønsberg Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 814,000
Operating profit NOK −39,000
Equity NOK 145,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−39k kr).

GE-MO AS is registered as a limited company in Tønsberg, Vestfold with organisation number 929414357. The business is classified under manufacture of other technical and industrial textiles (NACE 13.960). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon, reparasjon, salg og netthandel av båtkalesjer, industrisøm, markiser, salmakerartikler, båtutstyr 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 annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 814,000 in revenue and NOK −39,000 in operating profit.

Key figures · 2024

Revenue
NOK 814,000
Operating profit
NOK −39,000
Equity
NOK 145,000
Est. value
NOK 301,000

Financial health · 2024

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

Who owns GE-MO AS?

PER ARNE GEITLE
GE-MO AS
NOK 814,000 rev. · NOK −39,000 profit

GE-MO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GE-MO AS

Who owns GE-MO AS?

PER ARNE GEITLE is the largest registered owner, with 100.0%.

What is the revenue of GE-MO AS?

GE-MO AS had revenue of NOK 814,000 in 2024.

Where is GE-MO AS based?

GE-MO AS has its business address in Sem.

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.