BIZTRAC BETA
Wholesale of china and glassware and cleaning materials

VEVLE TRADE AS

Org. no. 932104180 Limited company (AS) Levanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −86,000
Equity NOK −215,000
Incorporated 2023
Share capital NOK 50,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−215k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−86k kr).

VEVLE TRADE AS is registered as a limited company in Levanger, Trøndelag with organisation number 932104180. The business is classified under wholesale of china and glassware and cleaning materials (NACE 46.440). The company was incorporated in 2023. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Salg av varer og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −86,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK −86,000
Equity
NOK −215,000

Financial health · 2025

Liquidity
2.47
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-86.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VEVLE TRADE AS?

ANDRÉ VEVLE AS
VEVLE TRADE AS
NOK 1.6m rev. · NOK −86,000 profit

VEVLE TRADE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEVLE TRADE AS

Who owns VEVLE TRADE AS?

ANDRÉ VEVLE AS is the largest registered owner, with 100.0%.

What is the revenue of VEVLE TRADE AS?

VEVLE TRADE AS had revenue of NOK 1.6m in 2025.

Who is the general manager of VEVLE TRADE AS?

André Vevle is registered as general manager of VEVLE TRADE AS.

Where is VEVLE TRADE AS based?

VEVLE TRADE AS has its business address in Levanger.

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.