BIZTRAC BETA
Business and other management consultancy activities

FINNPROSJEKT AS

Org. no. 915489079 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 858,000
Operating profit NOK 1,000
Equity NOK 1.1m
Incorporated 2015
Share capital NOK 30,000

FINNPROSJEKT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915489079. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 6 shares. The company's stated purpose is: “Salg av rådgivertjenester og prosjektutvikling med formål å fremme lønnsom utvikling og gjennomføring av nordiske samarbeidsprosjekter og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 858,000 in revenue and NOK 1,000 in operating profit.

Key figures · 2024

Revenue
NOK 858,000
Operating profit
NOK 1,000
Equity
NOK 1.1m
Est. value
NOK 531,000

Financial health · 2024

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

Who owns FINNPROSJEKT AS?

MARI KRISTINE VATN TAKALA
FINNPROSJEKT AS
NOK 858,000 rev. · NOK 1,000 profit

FINNPROSJEKT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FINNPROSJEKT AS

Who owns FINNPROSJEKT AS?

MARI KRISTINE VATN TAKALA is the largest registered owner, with 50.0%.

What is the revenue of FINNPROSJEKT AS?

FINNPROSJEKT AS had revenue of NOK 858,000 in 2024.

Who is the general manager of FINNPROSJEKT AS?

Jari Tero Kalevi Takala is registered as general manager of FINNPROSJEKT AS.

Where is FINNPROSJEKT AS based?

FINNPROSJEKT AS has its business address in Trondheim.

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.