biztrac. BETA
COMPANY REGISTER PROFILE
916132336 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Non-specialised retail sale of predominately food, beverages or tobacco

MULEN NÆR-MAT AS

Org. no. 916132336 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 19.5m
Operating profit NOK 463,000
Equity NOK 689,000
Incorporated 2015
Employees 8
Share capital NOK 30,000

MULEN NÆR-MAT AS is registered as a limited company in Bergen, Vestland with organisation number 916132336. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2015 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift av matbutikk.”. The most recent filed accounts, for the 2025 financial year, show NOK 19.5m in revenue and NOK 463,000 in operating profit.

Key figures · 2025

Revenue
NOK 19.5m
▼ −1 %
Operating profit
NOK 463,000
▼ −34 %
Equity
NOK 689,000
▲ +1 %
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
12.0%
Good
Return on total assets
Solidity
17.4%
Satisfactory
Equity as a share of total capital

Who owns MULEN NÆR-MAT AS?

MULEN NÆR-MAT AS
NOK 19.5m rev. · NOK 463,000 profit

MULEN NÆR-MAT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MULEN NÆR-MAT AS

Who owns MULEN NÆR-MAT AS?

ADHAMA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MULEN NÆR-MAT AS?

MULEN NÆR-MAT AS had revenue of NOK 19.5m in 2025.

Who is the general manager of MULEN NÆR-MAT AS?

Zigab Berhe Asfa is registered as general manager of MULEN NÆR-MAT AS.

Where is MULEN NÆR-MAT AS based?

MULEN NÆR-MAT AS has its business address in Bergen.

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.