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

VANGEN MAT DRIFT AS

Org. no. 814148572 Limited company (AS) Lier Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 45.1m
Operating profit NOK 579,000
Equity NOK 5.3m
Incorporated 2014
Employees 23
Share capital NOK 30,000

VANGEN MAT DRIFT AS is registered as a limited company in Lier, Buskerud with organisation number 814148572. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2014 and has 23 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Handel med dagligvarer og nærliggende produkter, også ved deltakelse I andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 45.1m in revenue and NOK 579,000 in operating profit.

Key figures · 2025

Revenue
NOK 45.1m
Operating profit
NOK 579,000
Equity
NOK 5.3m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns VANGEN MAT DRIFT AS?

ODD ARNE VANGEN
VANGEN MAT DRIFT AS
NOK 45.1m rev. · NOK 579,000 profit

VANGEN MAT DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VANGEN MAT DRIFT AS

Who owns VANGEN MAT DRIFT AS?

ODD ARNE VANGEN is the largest registered owner, with 100.0%.

What is the revenue of VANGEN MAT DRIFT AS?

VANGEN MAT DRIFT AS had revenue of NOK 45.1m in 2025.

Who is the general manager of VANGEN MAT DRIFT AS?

Odd Arne Vangen is registered as general manager of VANGEN MAT DRIFT AS.

Where is VANGEN MAT DRIFT AS based?

VANGEN MAT DRIFT AS has its business address in Sylling.

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.