BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

TEKNOPARTNER AS

Org. no. 915351492 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5,000
Equity NOK 424,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

TEKNOPARTNER AS is registered as a limited company in Bergen, Vestland with organisation number 915351492. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet/utleie av personell/investering eiendom og aksjer og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 424,000
Est. value
NOK 609,000

Financial health · 2024

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

Who owns TEKNOPARTNER AS?

ARILD SYNNEVÅG
TEKNOPARTNER AS
NOK 0 rev. · NOK −5,000 profit

TEKNOPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEKNOPARTNER AS

Who owns TEKNOPARTNER AS?

ARILD SYNNEVÅG is the largest registered owner, with 100.0%.

What is the revenue of TEKNOPARTNER AS?

TEKNOPARTNER AS had revenue of NOK 0 in 2024.

Who is the general manager of TEKNOPARTNER AS?

Arild Synnevåg is registered as general manager of TEKNOPARTNER AS.

Where is TEKNOPARTNER AS based?

TEKNOPARTNER AS has its business address in Hordvik.

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.