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

ERLINGS MATHUS AS

Org. no. 986327509 Limited company (AS) Kongsberg Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 39.9m
Operating profit NOK 1.2m
Equity NOK 2.2m
Incorporated 2003
Share capital NOK 350,000

ERLINGS MATHUS AS is registered as a limited company in Kongsberg, Buskerud with organisation number 986327509. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2003. Registered share capital is NOK 350,000, divided into 350 shares. The company's stated purpose is: “Dagligvarehandel, handel og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 39.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 39.9m
▼ −16 %
Operating profit
NOK 1.2m
▲ +60 %
Equity
NOK 2.2m
▲ +91 %
Est. value
NOK 5.8m

Financial health · 2025

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

Who owns ERLINGS MATHUS AS?

ERLINGS MATHUS AS
NOK 39.9m rev. · NOK 1.2m profit

ERLINGS MATHUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERLINGS MATHUS AS

Who owns ERLINGS MATHUS AS?

ERLING BAKKEN is the largest registered owner, with 100.0%.

What is the revenue of ERLINGS MATHUS AS?

ERLINGS MATHUS AS had revenue of NOK 39.9m in 2025.

Who is the general manager of ERLINGS MATHUS AS?

Erling Bakken is registered as general manager of ERLINGS MATHUS AS.

Where is ERLINGS MATHUS AS based?

ERLINGS MATHUS AS has its business address in Kongsberg.

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

Report a problem

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