biztrac. BETA
COMPANY REGISTER PROFILE
993358495 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

AMELTI HOLDING AS

Org. no. 993358495 Limited company (AS) Gjøvik Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK −12.0m
Incorporated 2008
Share capital NOK 102,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−12,0 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

AMELTI HOLDING AS is registered as a limited company in Gjøvik, Innlandet with organisation number 993358495. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2008. Registered share capital is NOK 102,000, divided into 10206 shares. The company's stated purpose is: “Eie og drive fast eiendom, være rettighetshaver av patenter, utleie av rettigheter, investere i andre selskaper, salg av tjenester, samt hva herved står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −6,000
▲ +7 %
Equity
NOK −12.0m
▼ −0 %
Est. value
NOK 787,000

Financial health · 2025

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

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

Who owns AMELTI HOLDING AS?

AMELTI HOLDING AS
· NOK −6,000 profit

AMELTI HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about AMELTI HOLDING AS

Who owns AMELTI HOLDING AS?

OPPLAND EIENDOM AS is the largest registered owner, with 40.0%.

Who is the general manager of AMELTI HOLDING AS?

Jørn Morten Kirkeby is registered as general manager of AMELTI HOLDING AS.

Where is AMELTI HOLDING AS based?

AMELTI HOLDING AS has its business address in Gjøvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.