BIZTRAC BETA
Rental and operating of own or leased real estate

VOSS TRAFIKKSKULE EIGEDOM AS

Org. no. 998676339 Limited company (AS) Voss Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 548,000
Operating profit NOK 346,000
Equity NOK 1.8m
Incorporated 2012
Share capital NOK 500,000

VOSS TRAFIKKSKULE EIGEDOM AS is registered as a limited company in Voss, Vestland with organisation number 998676339. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Investeringer, drift og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 548,000 in revenue and NOK 346,000 in operating profit.

Key figures · 2025

Revenue
NOK 548,000
Operating profit
NOK 346,000
Equity
NOK 1.8m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns VOSS TRAFIKKSKULE EIGEDOM AS?

LEKVEMOEN HOLDING AS
VOSS TRAFIKKSKULE EIGEDOM AS
NOK 548,000 rev. · NOK 346,000 profit

VOSS TRAFIKKSKULE EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOSS TRAFIKKSKULE EIGEDOM AS

Who owns VOSS TRAFIKKSKULE EIGEDOM AS?

LEKVEMOEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VOSS TRAFIKKSKULE EIGEDOM AS?

VOSS TRAFIKKSKULE EIGEDOM AS had revenue of NOK 548,000 in 2025.

Who is the general manager of VOSS TRAFIKKSKULE EIGEDOM AS?

Lars Nesheim-Hovda is registered as general manager of VOSS TRAFIKKSKULE EIGEDOM AS.

Where is VOSS TRAFIKKSKULE EIGEDOM AS based?

VOSS TRAFIKKSKULE EIGEDOM AS has its business address in Voss.

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.