BIZTRAC BETA
Manufacture of soft drinks and bottled waters

GRIMSTAD BRUSFABRIKK AS

Org. no. 921284683 Limited company (AS) Grimstad Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 262,000
Equity NOK 980,000
Incorporated 2018
Share capital NOK 30,000

GRIMSTAD BRUSFABRIKK AS is registered as a limited company in Grimstad, Agder with organisation number 921284683. The business is classified under manufacture of soft drinks and bottled waters (NACE 11.070). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikle, produsere og selge brus og mineralvann og tilhørende produkter og alt som er i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 262,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 262,000
Equity
NOK 980,000
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns GRIMSTAD BRUSFABRIKK AS?

KJETIL RØYSET JØRGENSEN
GRIMSTAD BRUSFABRIKK AS
NOK 3.6m rev. · NOK 262,000 profit

GRIMSTAD BRUSFABRIKK AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRIMSTAD BRUSFABRIKK AS

Who owns GRIMSTAD BRUSFABRIKK AS?

KJETIL RØYSET JØRGENSEN is the largest registered owner, with 25.0%.

What is the revenue of GRIMSTAD BRUSFABRIKK AS?

GRIMSTAD BRUSFABRIKK AS had revenue of NOK 3.6m in 2024.

Who is the general manager of GRIMSTAD BRUSFABRIKK AS?

Ida Konradsen is registered as general manager of GRIMSTAD BRUSFABRIKK AS.

Where is GRIMSTAD BRUSFABRIKK AS based?

GRIMSTAD BRUSFABRIKK AS has its business address in Grimstad.

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.