BIZTRAC BETA
Computer consultancy and computer facilities management activities

OMRM AS

Org. no. 916663943 Limited company (AS) Moss Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −27,000
Equity NOK 468,000
Incorporated 2016
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−27k kr).

OMRM AS is registered as a limited company in Moss, Østfold with organisation number 916663943. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2016. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Investering, kjøp og salg av aksjer, produkter og tjenester innen IT og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −27,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −27,000
Equity
NOK 468,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns OMRM AS?

OLE-MARTIN RASMUSSEN-MOSEID
OMRM AS
NOK 0 rev. · NOK −27,000 profit

OMRM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OMRM AS

Who owns OMRM AS?

OLE-MARTIN RASMUSSEN-MOSEID is the largest registered owner, with 100.0%.

What is the revenue of OMRM AS?

OMRM AS had revenue of NOK 0 in 2025.

Where is OMRM AS based?

OMRM AS has its business address in Moss.

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.