BIZTRAC BETA
Business and other management consultancy activities

VIGDA AS

Org. no. 916391439 Limited company (AS) Melhus Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 36,000
Operating profit NOK −85,000
Equity NOK 729,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−85k kr).

VIGDA AS is registered as a limited company in Melhus, Trøndelag with organisation number 916391439. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer / investering i andre selskaper, økonomisk og administrativ rådgivning, samt hva naturlig tilfaller.”. The most recent filed accounts, for the 2025 financial year, show NOK 36,000 in revenue and NOK −85,000 in operating profit.

Key figures · 2025

Revenue
NOK 36,000
Operating profit
NOK −85,000
Equity
NOK 729,000
Est. value
NOK 626,000

Financial health · 2025

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

Who owns VIGDA AS?

TOR ERIK LANGMO
VIGDA AS
NOK 36,000 rev. · NOK −85,000 profit

VIGDA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIGDA AS own?

VIGDA AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about VIGDA AS

Who owns VIGDA AS?

TOR ERIK LANGMO is the largest registered owner, with 100.0%.

What is the revenue of VIGDA AS?

VIGDA AS had revenue of NOK 36,000 in 2025.

Who is the general manager of VIGDA AS?

Tor Erik Langmo is registered as general manager of VIGDA AS.

Where is VIGDA AS based?

VIGDA AS has its business address in Melhus.

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.