BIZTRAC BETA
Retail sale of bread, cake and confectionery

GULSKOGEN BAKERI AS

Org. no. 929871502 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 12.4m
Operating profit NOK 550,000
Equity NOK 1.2m
Incorporated 2022
Employees 15
Share capital NOK 100,000

GULSKOGEN BAKERI AS is registered as a limited company in Drammen, Buskerud with organisation number 929871502. The business is classified under retail sale of bread, cake and confectionery (NACE 47.240). The company was incorporated in 2022 and has 15 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drift av bakeri, kafé, catering, event og konsulentoppdrag innenfor salg og service, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.4m in revenue and NOK 550,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.4m
Operating profit
NOK 550,000
Equity
NOK 1.2m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns GULSKOGEN BAKERI AS?

ELENI INVEST AS
GULSKOGEN BAKERI AS
NOK 12.4m rev. · NOK 550,000 profit

GULSKOGEN BAKERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULSKOGEN BAKERI AS

Who owns GULSKOGEN BAKERI AS?

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

What is the revenue of GULSKOGEN BAKERI AS?

GULSKOGEN BAKERI AS had revenue of NOK 12.4m in 2025.

Who is the general manager of GULSKOGEN BAKERI AS?

Eleni Gisholt Fanurakis is registered as general manager of GULSKOGEN BAKERI AS.

Where is GULSKOGEN BAKERI AS based?

GULSKOGEN BAKERI 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.