BIZTRAC BETA
Accounting and bookkeeping

M ØKONOMI AS

Org. no. 913012836 Limited company (AS) Rana Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK −133,000
Equity NOK 50,000
Incorporated 2013
Share capital NOK 50,000

Signals

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

M ØKONOMI AS is registered as a limited company in Rana, Nordland with organisation number 913012836. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2013. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Regnskapstjenester og andre tjenester som naturlig hører sammen med dette, herunder å delta på eiersiden i selskap som driver innen samme næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK −133,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK −133,000
Equity
NOK 50,000
Est. value
NOK 3.1m

Financial health · 2024

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns M ØKONOMI AS?

MEYERSHIP AS
M ØKONOMI AS
NOK 3.0m rev. · NOK −133,000 profit

M ØKONOMI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M ØKONOMI AS

Who owns M ØKONOMI AS?

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

What is the revenue of M ØKONOMI AS?

M ØKONOMI AS had revenue of NOK 3.0m in 2024.

Where is M ØKONOMI AS based?

M ØKONOMI AS has its business address in Mo I Rana.

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.