BIZTRAC BETA
Rental and operating of own or leased real estate

VEISTAD EIENDOM AS

Org. no. 914428343 Limited company (AS) Vågå Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 327,000
Operating profit NOK 135,000
Equity NOK −149,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−149k kr).

VEISTAD EIENDOM AS is registered as a limited company in Vågå, Innlandet with organisation number 914428343. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 327,000 in revenue and NOK 135,000 in operating profit.

Key figures · 2025

Revenue
NOK 327,000
Operating profit
NOK 135,000
Equity
NOK −149,000
Est. value
NOK 1.1m

Financial health · 2025

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

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

Who owns VEISTAD EIENDOM AS?

TROND KRISTOFFERSEN
VEISTAD EIENDOM AS
NOK 327,000 rev. · NOK 135,000 profit

VEISTAD EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEISTAD EIENDOM AS

Who owns VEISTAD EIENDOM AS?

TROND KRISTOFFERSEN is the largest registered owner, with 33.3%.

What is the revenue of VEISTAD EIENDOM AS?

VEISTAD EIENDOM AS had revenue of NOK 327,000 in 2025.

Who is the general manager of VEISTAD EIENDOM AS?

Roald Peder Kristoffersen is registered as general manager of VEISTAD EIENDOM AS.

Where is VEISTAD EIENDOM AS based?

VEISTAD EIENDOM AS has its business address in Vågå.

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.