BIZTRAC BETA
Plumbing installation

TEKNISK DRIFT OG EIENDOM AS

Org. no. 925237698 Limited company (AS) Lørenskog Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 100,000
Operating profit NOK 53,000
Equity NOK 74,000
Incorporated 2020
Share capital NOK 30,000

TEKNISK DRIFT OG EIENDOM AS is registered as a limited company in Lørenskog, Akershus with organisation number 925237698. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av tjenester og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 100,000 in revenue and NOK 53,000 in operating profit.

Key figures · 2024

Revenue
NOK 100,000
Operating profit
NOK 53,000
Equity
NOK 74,000
Est. value
NOK 197,000

Financial health · 2024

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

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

Who owns TEKNISK DRIFT OG EIENDOM AS?

LARS ROMAN HOLM
TEKNISK DRIFT OG EIENDOM AS
NOK 100,000 rev. · NOK 53,000 profit

TEKNISK DRIFT OG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TEKNISK DRIFT OG EIENDOM AS

Who owns TEKNISK DRIFT OG EIENDOM AS?

LARS ROMAN HOLM is the largest registered owner, with 50.0%.

What is the revenue of TEKNISK DRIFT OG EIENDOM AS?

TEKNISK DRIFT OG EIENDOM AS had revenue of NOK 100,000 in 2024.

Who is the general manager of TEKNISK DRIFT OG EIENDOM AS?

Lars Roman Holm is registered as general manager of TEKNISK DRIFT OG EIENDOM AS.

Where is TEKNISK DRIFT OG EIENDOM AS based?

TEKNISK DRIFT OG EIENDOM AS has its business address in Fjellhamar.

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.