BIZTRAC BETA
Wholesale of beverages

THE BREWERY GULSKOGEN AS

Org. no. 918415300 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 176,000
Equity NOK 717,000
Incorporated 2017
Employees 6
Share capital NOK 30,000

THE BREWERY GULSKOGEN AS is registered as a limited company in Drammen, Buskerud with organisation number 918415300. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 2017 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Selskapet skal operere med engrossalgs med drikkevarer med alkohol oppad til 4,7%”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 176,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 176,000
Equity
NOK 717,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns THE BREWERY GULSKOGEN AS?

JUTULEN INVEST AS
THE BREWERY GULSKOGEN AS
NOK 3.7m rev. · NOK 176,000 profit

THE BREWERY GULSKOGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about THE BREWERY GULSKOGEN AS

Who owns THE BREWERY GULSKOGEN AS?

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

What is the revenue of THE BREWERY GULSKOGEN AS?

THE BREWERY GULSKOGEN AS had revenue of NOK 3.7m in 2024.

Who is the general manager of THE BREWERY GULSKOGEN AS?

Per Øyvind Kristiansen is registered as general manager of THE BREWERY GULSKOGEN AS.

Where is THE BREWERY GULSKOGEN AS based?

THE BREWERY GULSKOGEN AS has its business address in Drammen.

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.