biztrac. BETA
COMPANY REGISTER PROFILE
913827252 ORG. NO. 2024 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of other food

MER SPARING AS

Org. no. 913827252 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 20.3m
Operating profit NOK 1.1m
Equity NOK 30,000
Incorporated 2014
Share capital NOK 30,000

MER SPARING AS is registered as a limited company in Oslo, Oslo with organisation number 913827252. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets virksomhet er salg av asiaprodukter, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.3m in revenue and NOK 1.1m in operating profit.

Former names: ASIAMAT AS

Key figures · 2024

Revenue
NOK 20.3m
▲ +196 %
Operating profit
NOK 1.1m
▼ −4 %
Equity
NOK 30,000
▲ +103 %
Est. value
NOK 3.7m

Financial health · 2024

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
23.1%
Very good
Return on total assets
Solidity
0.5%
Weak
Equity as a share of total capital

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

Who owns MER SPARING AS?

MER SPARING AS
NOK 20.3m rev. · NOK 1.1m profit

MER SPARING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MER SPARING AS

Who owns MER SPARING AS?

Jivan Abdelrahim is the largest registered owner, with 100.0%.

What is the revenue of MER SPARING AS?

MER SPARING AS had revenue of NOK 20.3m in 2024.

Who is the general manager of MER SPARING AS?

Jivan Abdelrahim is registered as general manager of MER SPARING AS.

Where is MER SPARING AS based?

MER SPARING AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.