BIZTRAC BETA
Buying and selling of own real estate

FRONT PROSJEKT AS

Org. no. 916860420 Limited company (AS) Tromsø Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 492,000
Operating profit NOK −895,000
Equity NOK 2.9m
Incorporated 2016
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−895k kr).

FRONT PROSJEKT AS is registered as a limited company in Tromsø, Troms with organisation number 916860420. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og utvikling av fast eiendom for salg og utleie og annen virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 492,000 in revenue and NOK −895,000 in operating profit.

Key figures · 2024

Revenue
NOK 492,000
Operating profit
NOK −895,000
Equity
NOK 2.9m
Est. value
NOK 2.7m

Financial health · 2024

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.3%
Weak
Equity as a share of total capital

Who owns FRONT PROSJEKT AS?

FRONT UTVIKLING AS
FRONT PROSJEKT AS
NOK 492,000 rev. · NOK −895,000 profit

FRONT PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRONT PROSJEKT AS

Who owns FRONT PROSJEKT AS?

FRONT UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of FRONT PROSJEKT AS?

FRONT PROSJEKT AS had revenue of NOK 492,000 in 2024.

Who is the general manager of FRONT PROSJEKT AS?

Teddy Leander Gamst is registered as general manager of FRONT PROSJEKT AS.

Where is FRONT PROSJEKT AS based?

FRONT PROSJEKT AS has its business address in Tromsø.

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.