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

BLINKEN MATHUS AS

Org. no. 983401023 Limited company (AS) Larvik Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 118.0m
Operating profit NOK 6.0m
Equity NOK 3.1m
Incorporated 2001
Employees 62
Share capital NOK 992,000

BLINKEN MATHUS AS is registered as a limited company in Larvik, Vestfold with organisation number 983401023. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2001 and has 62 registered employees. Registered share capital is NOK 992,000, divided into 992 shares. The company's stated purpose is: “Dagligvareforretning, samt alt som står i forbindelse med dette, herunder også å kunne delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 118.0m in revenue and NOK 6.0m in operating profit.

Key figures · 2024

Revenue
NOK 118.0m
Operating profit
NOK 6.0m
Equity
NOK 3.1m
Est. value
NOK 24.2m

Financial health · 2024

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

Who owns BLINKEN MATHUS AS?

NG MENY VESTFOLD TELEMARK AS
BLINKEN MATHUS AS
NOK 118.0m rev. · NOK 6.0m profit

BLINKEN MATHUS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BLINKEN MATHUS AS

Who owns BLINKEN MATHUS AS?

NG MENY VESTFOLD TELEMARK AS is the largest registered owner, with 49.0%.

What is the revenue of BLINKEN MATHUS AS?

BLINKEN MATHUS AS had revenue of NOK 118.0m in 2024.

Who is the general manager of BLINKEN MATHUS AS?

Rune Sleveland is registered as general manager of BLINKEN MATHUS AS.

Where is BLINKEN MATHUS AS based?

BLINKEN MATHUS AS has its business address in Larvik.

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.