BIZTRAC BETA
Rental and operating of own or leased real estate

TRON EIENDOM AS

Org. no. 998836735 Limited company (AS) Lillestrøm Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 665,000
Equity NOK 5.0m
Incorporated 2012
Share capital NOK 100,000

TRON EIENDOM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 998836735. 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 100,000, divided into 1000 shares. The company's stated purpose is: “Ved aksjetegning, eller annen deltagerinteresse, å etablere eierforhold i fast eiendom eller annen virksomhet. Likeens kjøp, salg og utleie av eiendom og utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 665,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 665,000
Equity
NOK 5.0m
Est. value
NOK 4.5m

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.7%
Good
Equity as a share of total capital

Who owns TRON EIENDOM AS?

TECPRO AS
TRON EIENDOM AS
NOK 2.4m rev. · NOK 665,000 profit

TRON EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Group structure

TRON EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about TRON EIENDOM AS

Who owns TRON EIENDOM AS?

TECPRO AS is the largest registered owner, with 50.1%.

What is the revenue of TRON EIENDOM AS?

TRON EIENDOM AS had revenue of NOK 2.4m in 2025.

Who is the general manager of TRON EIENDOM AS?

Geir Endre Bakkene is registered as general manager of TRON EIENDOM AS.

Where is TRON EIENDOM AS based?

TRON EIENDOM AS has its business address in Fetsund.

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.