BIZTRAC BETA
Manufacture of bread; manufacture of fresh pastry goods and cakes

BRUSTADBAKEREN AS

Org. no. 922421692 Limited company (AS) Klepp Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 11.1m
Operating profit NOK 794,000
Equity NOK 2.7m
Incorporated 2019
Employees 21
Share capital NOK 1.1m

BRUSTADBAKEREN AS is registered as a limited company in Klepp, Rogaland with organisation number 922421692. The business is classified under manufacture of bread; manufacture of fresh pastry goods and cakes (NACE 10.710). The company was incorporated in 2019 and has 21 registered employees. Registered share capital is NOK 1.1m, divided into 1100 shares. The company's stated purpose is: “Produksjon av bakeri- og konditorvarer, drift av bakeri- og konditoriutsalg samt eierinteresser i tilsvarende og andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.1m in revenue and NOK 794,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.1m
Operating profit
NOK 794,000
Equity
NOK 2.7m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns BRUSTADBAKEREN AS?

KSH INVEST AS
BRUSTADBAKEREN AS
NOK 11.1m rev. · NOK 794,000 profit

BRUSTADBAKEREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRUSTADBAKEREN AS

Who owns BRUSTADBAKEREN AS?

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

What is the revenue of BRUSTADBAKEREN AS?

BRUSTADBAKEREN AS had revenue of NOK 11.1m in 2024.

Who is the general manager of BRUSTADBAKEREN AS?

Tove Pedersen is registered as general manager of BRUSTADBAKEREN AS.

Where is BRUSTADBAKEREN AS based?

BRUSTADBAKEREN AS has its business address in Klepp Stasjon.

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.