BIZTRAC BETA
Manufacture of ceramic sanitary fixtures

BANO AS

Org. no. 980913023 Limited company (AS) Gloppen Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 95.1m
Operating profit NOK −17.5m
Equity NOK 47.1m
Incorporated 1999
Employees 55
Share capital NOK 1.4m

Signals

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

BANO AS is registered as a limited company in Gloppen, Vestland with organisation number 980913023. The business is classified under manufacture of ceramic sanitary fixtures (NACE 23.420). The company was incorporated in 1999 and has 55 registered employees. Registered share capital is NOK 1.4m, divided into 1389 shares. The company's stated purpose is: “Kjøp og salg av varer og tjenester, fast eiendom, aksjer samt industriell produksjon og produktutvikling. I tillegg alt som naturlig hører innunder ovennevnte.”. The most recent filed accounts, for the 2024 financial year, show NOK 95.1m in revenue and NOK −17.5m in operating profit.

Key figures · 2024

Revenue
NOK 95.1m
Operating profit
NOK −17.5m
Equity
NOK 47.1m
Est. value
NOK 62.0m

Financial health · 2024

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

Who owns BANO AS?

RETO INVEST AS
BANO AS
NOK 95.1m rev. · NOK −17.5m profit

BANO AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BANO AS er morselskap for 7 datterselskaper:

Frequently asked questions about BANO AS

Who owns BANO AS?

RETO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BANO AS?

BANO AS had revenue of NOK 95.1m in 2024.

Who is the general manager of BANO AS?

Stefan Jörg Barfeld is registered as general manager of BANO AS.

Where is BANO AS based?

BANO AS has its business address in Sandane.

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.