BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

AXFLOW SANDNES AS

Org. no. 976713974 Limited company (AS) Sandnes Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 26.1m
Operating profit NOK −2.9m
Equity NOK 7.6m
Incorporated 1996
Employees 8
Share capital NOK 624,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,9 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AXFLOW SANDNES AS is registered as a limited company in Sandnes, Rogaland with organisation number 976713974. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 1996 and has 8 registered employees. Registered share capital is NOK 624,000, divided into 31200 shares. The company's stated purpose is: “Handel, agenturvirksomhet, service, eksport og import.”. The most recent filed accounts, for the 2025 financial year, show NOK 26.1m in revenue and NOK −2.9m in operating profit.

Key figures · 2025

Revenue
NOK 26.1m
Operating profit
NOK −2.9m
Equity
NOK 7.6m
Est. value
NOK 12.1m

Financial health · 2025

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

Who owns AXFLOW SANDNES AS?

AXFLOW AS
AXFLOW SANDNES AS
NOK 26.1m rev. · NOK −2.9m profit

AXFLOW SANDNES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AXFLOW SANDNES AS

Who owns AXFLOW SANDNES AS?

AXFLOW AS is the largest registered owner, with 100.0%.

What is the revenue of AXFLOW SANDNES AS?

AXFLOW SANDNES AS had revenue of NOK 26.1m in 2025.

Where is AXFLOW SANDNES AS based?

AXFLOW SANDNES AS has its business address in Sandnes.

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.