BIZTRAC BETA
Rental and operating of own or leased real estate

LEV VEL EIENDOM AS

Org. no. 886746172 Limited company (AS) Stjørdal Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 304,000
Operating profit NOK 171,000
Equity NOK 471,000
Incorporated 2004
Share capital NOK 102,000

LEV VEL EIENDOM AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 886746172. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Handel, forvaltning av fast eiendom, løsøre og verdipapirer, finansvirksomhet, samt ved aksjer og parter å delta i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 304,000 in revenue and NOK 171,000 in operating profit.

Key figures · 2024

Revenue
NOK 304,000
Operating profit
NOK 171,000
Equity
NOK 471,000
Est. value
NOK 531,000

Financial health · 2024

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.0%
Good
Equity as a share of total capital

Who owns LEV VEL EIENDOM AS?

ROY TINGSTAD
LEV VEL EIENDOM AS
NOK 304,000 rev. · NOK 171,000 profit

LEV VEL EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEV VEL EIENDOM AS

Who owns LEV VEL EIENDOM AS?

ROY TINGSTAD is the largest registered owner, with 33.3%.

What is the revenue of LEV VEL EIENDOM AS?

LEV VEL EIENDOM AS had revenue of NOK 304,000 in 2024.

Who is the general manager of LEV VEL EIENDOM AS?

Arve Solum is registered as general manager of LEV VEL EIENDOM AS.

Where is LEV VEL EIENDOM AS based?

LEV VEL EIENDOM AS has its business address in Stjø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.