BIZTRAC BETA
Wholesale of other intermediate products

VEFI AS

Org. no. 848690112 Limited company (AS) Drammen Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 72.7m
Operating profit NOK −1.2m
Equity NOK 2.5m
Incorporated 1988
Employees 5
Share capital NOK 171,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).

VEFI AS is registered as a limited company in Drammen, Buskerud with organisation number 848690112. The business is classified under wholesale of other intermediate products (NACE 46.860). The company was incorporated in 1988 and has 5 registered employees. Registered share capital is NOK 171,000, divided into 1140 shares. The company's stated purpose is: “Handel, tilvirking og virksomhet, investering i eiendom, aksjer og andre verdipapirer samt annen virksomhet som står i forbindelse med dette herunder å eie eller delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 72.7m in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 72.7m
Operating profit
NOK −1.2m
Equity
NOK 2.5m
Est. value
NOK 19.0m

Financial health · 2024

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

Who owns VEFI AS?

FIRMUM AB
VEFI AS
NOK 72.7m rev. · NOK −1.2m profit

VEFI AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VEFI AS er morselskap for 1 datterselskap:

Frequently asked questions about VEFI AS

Who owns VEFI AS?

FIRMUM AB is the largest registered owner, with 100.0%.

What is the revenue of VEFI AS?

VEFI AS had revenue of NOK 72.7m in 2024.

Who is the general manager of VEFI AS?

Erik Osborne Chapman is registered as general manager of VEFI AS.

Where is VEFI AS based?

VEFI AS has its business address in Drammen.

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.