BIZTRAC BETA
Rental and operating of own or leased real estate

FJT EIENDOM AS

Org. no. 912586804 Limited company (AS) Melhus Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 521,000
Equity NOK 373,000
Incorporated 2013
Share capital NOK 300,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FJT EIENDOM AS is registered as a limited company in Melhus, Trøndelag with organisation number 912586804. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Salg og utleie av fast eiendom, samt ved aksjeeie eller på annen måte gjøre seg interessert i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 521,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 521,000
Equity
NOK 373,000
Est. value
NOK 783,000

Financial health · 2024

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

Who owns FJT EIENDOM AS?

AJO INVEST AS
FJT EIENDOM AS
NOK 1.1m rev. · NOK 521,000 profit

FJT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FJT EIENDOM AS

Who owns FJT EIENDOM AS?

AJO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of FJT EIENDOM AS?

FJT EIENDOM AS had revenue of NOK 1.1m in 2024.

Who is the general manager of FJT EIENDOM AS?

John Forseth is registered as general manager of FJT EIENDOM AS.

Where is FJT EIENDOM AS based?

FJT EIENDOM AS has its business address in Melhus.

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.