BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

QUIPBROKERS AS

Org. no. 988734055 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK −1.3m
Equity NOK 1.0m
Incorporated 2005
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,3 mill kr).

QUIPBROKERS AS is registered as a limited company in Bergen, Vestland with organisation number 988734055. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Drive megling (vareagent) og handel (vareomsetning) med løsøre innenfor industri-, skips- og offshorenæring, samt å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK −1.3m in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK −1.3m
Equity
NOK 1.0m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns QUIPBROKERS AS?

QUIPS AS
QUIPBROKERS AS
NOK 4.9m rev. · NOK −1.3m profit

QUIPBROKERS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about QUIPBROKERS AS

Who owns QUIPBROKERS AS?

QUIPS AS is the largest registered owner, with 92.0%.

What is the revenue of QUIPBROKERS AS?

QUIPBROKERS AS had revenue of NOK 4.9m in 2024.

Who is the general manager of QUIPBROKERS AS?

Trond Jarle Bjørsvik is registered as general manager of QUIPBROKERS AS.

Where is QUIPBROKERS AS based?

QUIPBROKERS AS has its business address in Eidsvågneset.

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.