BIZTRAC BETA
Other technical consultancy

VEDELD TECHNOLOGY

Org. no. 919957115 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 78,000
Incorporated 2017
Share capital NOK 1.1m

Signals

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

VEDELD TECHNOLOGY is registered as a limited company in Bærum, Akershus with organisation number 919957115. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 1.1m, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utvikling og produksjon av komponenter innen hydraulikk, industri og offshore, samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 78,000
Est. value
NOK 127,000

Financial health · 2025

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

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

Who owns VEDELD TECHNOLOGY?

VEDELD AS
VEDELD TECHNOLOGY
NOK 0 rev. · NOK −16,000 profit

VEDELD TECHNOLOGY has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEDELD TECHNOLOGY

Who owns VEDELD TECHNOLOGY?

VEDELD AS is the largest registered owner, with 100.0%.

What is the revenue of VEDELD TECHNOLOGY?

VEDELD TECHNOLOGY had revenue of NOK 0 in 2025.

Who is the general manager of VEDELD TECHNOLOGY?

Henrik Vedeld is registered as general manager of VEDELD TECHNOLOGY.

Where is VEDELD TECHNOLOGY based?

VEDELD TECHNOLOGY has its business address in Lysaker.

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.