biztrac. BETA
COMPANY REGISTER PROFILE
919399627 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Wholesale of wood, construction materials and sanitary equipment

BACH-GANSMO AS

Org. no. 919399627 Limited company (AS) Ullensaker Incorporated 2017 Active
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 4.8m
Incorporated 2017
Share capital NOK 30,000

BACH-GANSMO AS is registered as a limited company in Ullensaker, Akershus with organisation number 919399627. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 4.8m
▼ −47 %
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns BACH-GANSMO AS?

BACH-GANSMO AS
NOK 0 rev. · NOK 0 profit

BACH-GANSMO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BACH-GANSMO AS own?

BACH-GANSMO AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about BACH-GANSMO AS

Who owns BACH-GANSMO AS?

Ola Bach-Gansmo is the largest registered owner, with 100.0%.

What is the revenue of BACH-GANSMO AS?

BACH-GANSMO AS had revenue of NOK 0 in 2025.

Who is the general manager of BACH-GANSMO AS?

Ola Bach-Gansmo is registered as general manager of BACH-GANSMO AS.

Where is BACH-GANSMO AS based?

BACH-GANSMO AS has its business address in Jessheim.

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

Report a problem

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