BIZTRAC BETA
Wholesale of machine tools

ING YNGVE EGE AS

Org. no. 943917752 Limited company (AS) Oslo Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 68.9m
Operating profit NOK 1.9m
Equity NOK 13.3m
Incorporated 1986
Employees 9
Share capital NOK 560,000

Signals

1 flags
  • Nylig endring 2026-02-03 Adresseendring registrert 2026-02-03.

ING YNGVE EGE AS is registered as a limited company in Oslo, Oslo with organisation number 943917752. The business is classified under wholesale of machine tools (NACE 46.620). The company was incorporated in 1986 and has 9 registered employees. Registered share capital is NOK 560,000, divided into 1000 shares. The company's stated purpose is: “Handel, samt deltagelse i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 68.9m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 68.9m
Operating profit
NOK 1.9m
Equity
NOK 13.3m
Est. value
NOK 14.0m

Financial health · 2024

Liquidity
1.60
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
43.6%
Very good
Equity as a share of total capital

Who owns ING YNGVE EGE AS?

EGE-GRUPPEN AS
ING YNGVE EGE AS
NOK 68.9m rev. · NOK 1.9m profit

ING YNGVE EGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ING YNGVE EGE AS own?

ING YNGVE EGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ING YNGVE EGE AS

Who owns ING YNGVE EGE AS?

EGE-GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of ING YNGVE EGE AS?

ING YNGVE EGE AS had revenue of NOK 68.9m in 2024.

Who is the general manager of ING YNGVE EGE AS?

Tor Even Bjørnvold is registered as general manager of ING YNGVE EGE AS.

Where is ING YNGVE EGE AS based?

ING YNGVE EGE AS has its business address in Oslo.

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.