BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

AJ MATBUTIKK AS

Org. no. 916309732 Limited company (AS) Sør-Varanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 8.1m
Operating profit NOK 8,000
Equity NOK 418,000
Incorporated 2015
Employees 17
Share capital NOK 30,000

AJ MATBUTIKK AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 916309732. 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 17 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Butikkdrift dagligvarer og take away food. Selskapet skal også kunne investere i annen eller lignende næringslivsaktivitet.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.1m in revenue and NOK 8,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.1m
Operating profit
NOK 8,000
Equity
NOK 418,000
Est. value
NOK 223,000

Financial health · 2025

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.0%
Good
Equity as a share of total capital

Who owns AJ MATBUTIKK AS?

JERRICK GAON SIBAYAN
AJ MATBUTIKK AS
NOK 8.1m rev. · NOK 8,000 profit

AJ MATBUTIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AJ MATBUTIKK AS

Who owns AJ MATBUTIKK AS?

JERRICK GAON SIBAYAN is the largest registered owner, with 50.0%.

What is the revenue of AJ MATBUTIKK AS?

AJ MATBUTIKK AS had revenue of NOK 8.1m in 2025.

Who is the general manager of AJ MATBUTIKK AS?

Jerrick Gaon Sibayan is registered as general manager of AJ MATBUTIKK AS.

Where is AJ MATBUTIKK AS based?

AJ MATBUTIKK AS has its business address in Kirkenes.

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.