BIZTRAC BETA
Intermediation service activities for real estate activities

FRONTLINE FOLLO AS

Org. no. 921831382 Limited company (AS) Ås Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 32.8m
Operating profit NOK 7.4m
Equity NOK 6.0m
Incorporated 2018
Employees 11
Share capital NOK 300,000

FRONTLINE FOLLO AS is registered as a limited company in Ås, Akershus with organisation number 921831382. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2018 and has 11 registered employees. Registered share capital is NOK 300,000, divided into 2400 shares. The company's stated purpose is: “Eiendomsmegling.”. The most recent filed accounts, for the 2024 financial year, show NOK 32.8m in revenue and NOK 7.4m in operating profit.

Key figures · 2024

Revenue
NOK 32.8m
Operating profit
NOK 7.4m
Equity
NOK 6.0m
Est. value
NOK 21.6m

Financial health · 2024

Liquidity
1.74
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.2%
Very good
Equity as a share of total capital

Who owns FRONTLINE FOLLO AS?

SHARMA EIENDOM AS
FRONTLINE FOLLO AS
NOK 32.8m rev. · NOK 7.4m profit

FRONTLINE FOLLO AS has 4 registered shareholders:

All shareholders and roles →

Which companies does FRONTLINE FOLLO AS own?

FRONTLINE FOLLO AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about FRONTLINE FOLLO AS

Who owns FRONTLINE FOLLO AS?

SHARMA EIENDOM AS is the largest registered owner, with 61.0%.

What is the revenue of FRONTLINE FOLLO AS?

FRONTLINE FOLLO AS had revenue of NOK 32.8m in 2024.

Who is the general manager of FRONTLINE FOLLO AS?

Amit Kumar Sharma is registered as general manager of FRONTLINE FOLLO AS.

Where is FRONTLINE FOLLO AS based?

FRONTLINE FOLLO AS has its business address in Ås.

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.