BIZTRAC BETA
Buying and selling of own real estate

DEVEG EIENDOM AS

Org. no. 920158749 Limited company (AS) Rollag Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 2.6m
Equity NOK 3.2m
Incorporated 2017
Share capital NOK 100,000

DEVEG EIENDOM AS is registered as a limited company in Rollag, Buskerud with organisation number 920158749. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 2.6m in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 2.6m
Equity
NOK 3.2m
Est. value
NOK 7.0m

Financial health · 2024

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

Who owns DEVEG EIENDOM AS?

TORSTEIN LINDHEIM
DEVEG EIENDOM AS
NOK 3.3m rev. · NOK 2.6m profit

DEVEG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does DEVEG EIENDOM AS own?

DEVEG EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DEVEG EIENDOM AS

Who owns DEVEG EIENDOM AS?

TORSTEIN LINDHEIM is the largest registered owner, with 51.0%.

What is the revenue of DEVEG EIENDOM AS?

DEVEG EIENDOM AS had revenue of NOK 3.3m in 2025.

Who is the general manager of DEVEG EIENDOM AS?

Torstein Lindheim is registered as general manager of DEVEG EIENDOM AS.

Where is DEVEG EIENDOM AS based?

DEVEG EIENDOM AS has its business address in Veggli.

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.