BIZTRAC BETA
Casting of other non-ferrous metals

VESTAD NÆRINGSEIENDOM AS

Org. no. 919365390 Limited company (AS) Elverum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 414,000
Operating profit NOK 287,000
Equity NOK 122,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VESTAD NÆRINGSEIENDOM AS is registered as a limited company in Elverum, Innlandet with organisation number 919365390. The business is classified under casting of other non-ferrous metals (NACE 24.540). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i eiendommer, drift av eiendommer og annen virksomhet som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 414,000 in revenue and NOK 287,000 in operating profit.

Key figures · 2024

Revenue
NOK 414,000
Operating profit
NOK 287,000
Equity
NOK 122,000
Est. value
NOK 697,000

Financial health · 2024

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

Who owns VESTAD NÆRINGSEIENDOM AS?

NORSE INDUSTRIES AS
VESTAD NÆRINGSEIENDOM AS
NOK 414,000 rev. · NOK 287,000 profit

VESTAD NÆRINGSEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTAD NÆRINGSEIENDOM AS

Who owns VESTAD NÆRINGSEIENDOM AS?

NORSE INDUSTRIES AS is the largest registered owner, with 100.0%.

What is the revenue of VESTAD NÆRINGSEIENDOM AS?

VESTAD NÆRINGSEIENDOM AS had revenue of NOK 414,000 in 2024.

Where is VESTAD NÆRINGSEIENDOM AS based?

VESTAD NÆRINGSEIENDOM AS has its business address in Elverum.

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.