BIZTRAC BETA
Rental and operating of own or leased real estate

FRONT EIENDOM AS

Org. no. 983226051 Limited company (AS) Melhus Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 665,000
Operating profit NOK 181,000
Equity NOK 1.8m
Incorporated 2001
Share capital NOK 100,000

FRONT EIENDOM AS is registered as a limited company in Melhus, Trøndelag with organisation number 983226051. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå utvikling, utleie og drift av eiendom, investeringsvirksomhet og annen virksomhet beslektet med denne. Samt detaljhandel med biler og lette motorvogner, unntatt motorsykler og utøve bedriftsrådgivning og annen administrativ rådgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 665,000 in revenue and NOK 181,000 in operating profit.

Key figures · 2024

Revenue
NOK 665,000
Operating profit
NOK 181,000
Equity
NOK 1.8m
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns FRONT EIENDOM AS?

FRONT1 AS
FRONT EIENDOM AS
NOK 665,000 rev. · NOK 181,000 profit

FRONT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRONT EIENDOM AS

Who owns FRONT EIENDOM AS?

FRONT1 AS is the largest registered owner, with 100.0%.

What is the revenue of FRONT EIENDOM AS?

FRONT EIENDOM AS had revenue of NOK 665,000 in 2024.

Where is FRONT EIENDOM AS based?

FRONT EIENDOM AS has its business address in Hovin I Gauldal.

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.