BIZTRAC BETA
Wholesale of other machinery and equipment

BAGGES AS

Org. no. 980616622 Limited company (AS) Lillestrøm Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 282.2m
Operating profit NOK 63.1m
Equity NOK 30.4m
Incorporated 1999
Employees 41
Share capital NOK 623,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BAGGES AS is registered as a limited company in Lillestrøm, Akershus with organisation number 980616622. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1999 and has 41 registered employees. Registered share capital is NOK 623,000, divided into 83 shares. The company's stated purpose is: “Handel, agentur og produksjonsvirksomhet samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 282.2m in revenue and NOK 63.1m in operating profit.

Key figures · 2025

Revenue
NOK 282.2m
Operating profit
NOK 63.1m
Equity
NOK 30.4m
Est. value
NOK 210.9m

Financial health · 2025

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

Who owns BAGGES AS?

NEGOTIUM AS
BAGGES AS
NOK 282.2m rev. · NOK 63.1m profit

BAGGES AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BAGGES AS er morselskap for 2 datterselskaper:

Frequently asked questions about BAGGES AS

Who owns BAGGES AS?

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

What is the revenue of BAGGES AS?

BAGGES AS had revenue of NOK 282.2m in 2025.

Who is the general manager of BAGGES AS?

Geir Gudmundsen is registered as general manager of BAGGES AS.

Where is BAGGES AS based?

BAGGES AS has its business address in Skedsmokorset.

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.