BIZTRAC BETA
Rental and operating of own or leased real estate

VEISTASJONEN EIENDOM AS

Org. no. 992946229 Limited company (AS) Drangedal Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 65,000
Operating profit NOK 721
Equity NOK 195,000
Incorporated 2008
Share capital NOK 100,000

VEISTASJONEN EIENDOM AS is registered as a limited company in Drangedal, Telemark with organisation number 992946229. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i fast eiendom og utleie av denne samt investering i andre selskaper og kjøp av driftsmidler for utleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 65,000 in revenue and NOK 721 in operating profit.

Key figures · 2024

Revenue
NOK 65,000
Operating profit
NOK 721
Equity
NOK 195,000
Est. value
NOK 136,000

Financial health · 2024

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

Who owns VEISTASJONEN EIENDOM AS?

SIGBJØRN DAHLE
VEISTASJONEN EIENDOM AS
NOK 65,000 rev. · NOK 721 profit

VEISTASJONEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEISTASJONEN EIENDOM AS

Who owns VEISTASJONEN EIENDOM AS?

SIGBJØRN DAHLE is the largest registered owner, with 50.0%.

What is the revenue of VEISTASJONEN EIENDOM AS?

VEISTASJONEN EIENDOM AS had revenue of NOK 65,000 in 2024.

Who is the general manager of VEISTASJONEN EIENDOM AS?

Sigbjørn Dahle is registered as general manager of VEISTASJONEN EIENDOM AS.

Where is VEISTASJONEN EIENDOM AS based?

VEISTASJONEN EIENDOM AS has its business address in Tørdal.

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.