biztrac. BETA
COMPANY REGISTER PROFILE
920512879 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TV 26 EIENDOM AS

Org. no. 920512879 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 24.2m
Operating profit NOK 13.8m
Equity NOK 79.9m
Incorporated 2017
Share capital NOK 4.6m

TV 26 EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920512879. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 4.6m, divided into 4590164 shares. The company's stated purpose is: “Drift av fast eiendom, herunder kjøp og salg, utvikling, drift og annen aktivitet knyttet til fast eiendom, samt annen virksomhet beslektet med dette, herunder investeringer i aksjer og andeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 24.2m in revenue and NOK 13.8m in operating profit.

Former names: CENTRES DEVELOPMENT AS

Key figures · 2025

Revenue
NOK 24.2m
▲ +3 %
Operating profit
NOK 13.8m
▲ +7 %
Equity
NOK 79.9m
▲ +3136 %
Est. value
NOK 76.2m

Financial health · 2025

Liquidity
56.87
Very good
Current assets ÷ current liabilities
Profitability
4.1%
Weak
Return on total assets
Solidity
22.9%
Good
Equity as a share of total capital

Who owns TV 26 EIENDOM AS?

TV 26 EIENDOM AS
NOK 24.2m rev. · NOK 13.8m profit

TV 26 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TV 26 EIENDOM AS

Who owns TV 26 EIENDOM AS?

SLK PROPERTY AS is the largest registered owner, with 100.0%.

What is the revenue of TV 26 EIENDOM AS?

TV 26 EIENDOM AS had revenue of NOK 24.2m in 2025.

Where is TV 26 EIENDOM AS based?

TV 26 EIENDOM AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.