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

KLEPSVIK MAT AS

Org. no. 912775267 Limited company (AS) Øygarden Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 67.8m
Operating profit NOK 5.2m
Equity NOK 25.2m
Incorporated 2013
Employees 26
Share capital NOK 320,000

KLEPSVIK MAT AS is registered as a limited company in Øygarden, Vestland with organisation number 912775267. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2013 and has 26 registered employees. Registered share capital is NOK 320,000, divided into 800 shares. The company's stated purpose is: “Butikkhandel med hovedvekt på nærings og nytelsesmidler samt annen næringsvirksomhet relatert til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 67.8m in revenue and NOK 5.2m in operating profit.

Key figures · 2025

Revenue
NOK 67.8m
▲ +3 %
Operating profit
NOK 5.2m
▲ +17 %
Equity
NOK 25.2m
▲ +14 %
Est. value
NOK 34.4m

Financial health · 2025

Liquidity
3.27
Very good
Current assets ÷ current liabilities
Profitability
22.9%
Very good
Return on total assets
Solidity
74.5%
Very good
Equity as a share of total capital

Who owns KLEPSVIK MAT AS?

KLEPSVIK MAT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KLEPSVIK MAT AS

Who owns KLEPSVIK MAT AS?

VIDAR KLEPSVIK is the largest registered owner, with 55.0%.

What is the revenue of KLEPSVIK MAT AS?

KLEPSVIK MAT AS had revenue of NOK 67.8m in 2025.

Who is the general manager of KLEPSVIK MAT AS?

Vidar Klepsvik is registered as general manager of KLEPSVIK MAT AS.

Where is KLEPSVIK MAT AS based?

KLEPSVIK MAT AS has its business address in Steinsland.

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.