BIZTRAC BETA
Processing and preserving of meat, except of poultry meat

VINGELEN WAGYU AS

Org. no. 931353853 Limited company (AS) Tolga Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 233,000
Operating profit NOK −53,000
Equity NOK 38,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−53k kr).

VINGELEN WAGYU AS is registered as a limited company in Tolga, Innlandet with organisation number 931353853. The business is classified under processing and preserving of meat, except of poultry meat (NACE 10.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøpe og selge kjøtt av rasen Wagyu som er avlet opp på naturgitte norske bærekraftige ressurser ved hjelp av beiting og grasproduksjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 233,000 in revenue and NOK −53,000 in operating profit.

Key figures · 2024

Revenue
NOK 233,000
Operating profit
NOK −53,000
Equity
NOK 38,000
Est. value
NOK 145,000

Financial health · 2025

Liquidity
-35.36
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
102.8%
Weak
Equity as a share of total capital

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

Who owns VINGELEN WAGYU AS?

SVEINAR AASTRØEN
VINGELEN WAGYU AS
NOK 233,000 rev. · NOK −53,000 profit

VINGELEN WAGYU AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VINGELEN WAGYU AS

Who owns VINGELEN WAGYU AS?

SVEINAR AASTRØEN is the largest registered owner, with 50.0%.

What is the revenue of VINGELEN WAGYU AS?

VINGELEN WAGYU AS had revenue of NOK 233,000 in 2024.

Where is VINGELEN WAGYU AS based?

VINGELEN WAGYU AS has its business address in Vingelen.

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.