BIZTRAC BETA
Civil engineering activities

AS PROSJEKTTJENESTER

Org. no. 956729270 Limited company (AS) Bergen Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 500,000
Operating profit NOK 49,000
Equity NOK 86,000
Incorporated 1990
Share capital NOK 100,000

AS PROSJEKTTJENESTER is registered as a limited company in Bergen, Vestland with organisation number 956729270. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1990. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive forretningsmessig virksomhet av enhver art, særlig prosjektering og prosjektbeskrivelser, byggeadministrasjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 500,000 in revenue and NOK 49,000 in operating profit.

Key figures · 2024

Revenue
NOK 500,000
Operating profit
NOK 49,000
Equity
NOK 86,000
Est. value
NOK 288,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AS PROSJEKTTJENESTER?

COLLEGIUM RÅDGIVNING AS
AS PROSJEKTTJENESTER
NOK 500,000 rev. · NOK 49,000 profit

AS PROSJEKTTJENESTER has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AS PROSJEKTTJENESTER

Who owns AS PROSJEKTTJENESTER?

COLLEGIUM RÅDGIVNING AS is the largest registered owner, with 100.0%.

What is the revenue of AS PROSJEKTTJENESTER?

AS PROSJEKTTJENESTER had revenue of NOK 500,000 in 2024.

Who is the general manager of AS PROSJEKTTJENESTER?

Dag Magne Vedvik is registered as general manager of AS PROSJEKTTJENESTER.

Where is AS PROSJEKTTJENESTER based?

AS PROSJEKTTJENESTER has its business address in Fana.

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.