BIZTRAC BETA
COMPANY REGISTER PROFILE
918783113 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Site preparation

QUICKPUMP AS

Org. no. 918783113 Limited company (AS) Kvinesdal Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −26,000
Equity NOK 724,000
Incorporated 2017
Share capital NOK 210,000

Signals

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

QUICKPUMP AS is registered as a limited company in Kvinesdal, Agder with organisation number 918783113. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017. Registered share capital is NOK 210,000, divided into 300 shares. The company's stated purpose is: “Anleggsvirksomhet.”.

Key figures · 2024

Operating profit
NOK −26,000
Equity
NOK 724,000
Est. value
NOK 650,000

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.5%
Satisfactory
Equity as a share of total capital

Who owns QUICKPUMP AS?

QUICKPUMP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about QUICKPUMP AS

Who owns QUICKPUMP AS?

HEILE AS is the largest registered owner, with 41.0%.

Who is the general manager of QUICKPUMP AS?

Martin Eftestøl is registered as general manager of QUICKPUMP AS.

Where is QUICKPUMP AS based?

QUICKPUMP AS has its business address in Øyestranda.

Property

Business address Industrivegen 9, 4484 Øyestranda
Cadastral unit 4227-113/285/0/0
Building Lagerhall · 2 units

8 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.