BIZTRAC BETA
Wholesale of other machinery and equipment

ELVESKOG AS

Org. no. 920997465 Limited company (AS) Nordreisa Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 66,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

ELVESKOG AS is registered as a limited company in Nordreisa, Troms with organisation number 920997465. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøpe, eie og selge aksjer, obligasjoner og andre finansielle instrumenter og alt som er beslektet eller står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 66,000
Est. value
NOK 278,000

Financial health · 2025

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

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

Who owns ELVESKOG AS?

MORTEN ALEKSANDER ELVESKOG
ELVESKOG AS
NOK 0 rev. · NOK −6,000 profit

ELVESKOG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ELVESKOG AS own?

ELVESKOG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ELVESKOG AS

Who owns ELVESKOG AS?

MORTEN ALEKSANDER ELVESKOG is the largest registered owner, with 100.0%.

What is the revenue of ELVESKOG AS?

ELVESKOG AS had revenue of NOK 0 in 2025.

Where is ELVESKOG AS based?

ELVESKOG AS has its business address in Storslett.

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.