BIZTRAC BETA
Wholesale of other machinery and equipment

BEST-PARTNER AS

Org. no. 959622191 Limited company (AS) Malvik Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 554,000
Operating profit NOK −30,000
Equity NOK 322,000
Incorporated 1991
Share capital NOK 100,000

Signals

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

BEST-PARTNER AS is registered as a limited company in Malvik, Trøndelag with organisation number 959622191. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg & service av serveringsmaskiner samt ingredienser til disse. Bilutleie av personbiler/varebiler/lastebiler. Godsdistribusjon. Import av konfeksjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 554,000 in revenue and NOK −30,000 in operating profit.

Key figures · 2024

Revenue
NOK 554,000
Operating profit
NOK −30,000
Equity
NOK 322,000
Est. value
NOK 333,000

Financial health · 2024

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

Who owns BEST-PARTNER AS?

TERJE HUNNESTAD
BEST-PARTNER AS
NOK 554,000 rev. · NOK −30,000 profit

BEST-PARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEST-PARTNER AS

Who owns BEST-PARTNER AS?

TERJE HUNNESTAD is the largest registered owner, with 100.0%.

What is the revenue of BEST-PARTNER AS?

BEST-PARTNER AS had revenue of NOK 554,000 in 2024.

Who is the general manager of BEST-PARTNER AS?

Terje Hunnestad is registered as general manager of BEST-PARTNER AS.

Where is BEST-PARTNER AS based?

BEST-PARTNER AS has its business address in Malvik.

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.