BIZTRAC BETA
Development of building projects

TF BOLIGUTVIKLING AS

Org. no. 916293798 Limited company (AS) Stjørdal Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −4.1m
Equity NOK −16.9m
Incorporated 2015
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−16,9 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4,1 mill kr).
  • Nylig endring 2026-07-08 Adresseendring registrert 2026-07-08.

TF BOLIGUTVIKLING AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 916293798. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsselskap, herunder å investere i aksjer, obligasjoner, fast eiendom, andeler i selskap etter selskapsloven og annet som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −4.1m
Equity
NOK −16.9m

Financial health · 2025

Liquidity
23.56
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-18.0%
Weak
Equity as a share of total capital

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

Who owns TF BOLIGUTVIKLING AS?

STJØRDAL BOLIGUTVIKLING AS
TF BOLIGUTVIKLING AS
· NOK −4.1m profit

TF BOLIGUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TF BOLIGUTVIKLING AS own?

TF BOLIGUTVIKLING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about TF BOLIGUTVIKLING AS

Who owns TF BOLIGUTVIKLING AS?

STJØRDAL BOLIGUTVIKLING AS is the largest registered owner, with 50.0%.

Where is TF BOLIGUTVIKLING AS based?

TF BOLIGUTVIKLING 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.