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

SLOTTSKAKER AS

Org. no. 989051849 Limited company (AS) Åmli Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −241,000
Equity NOK 4.4m
Incorporated 2005
Share capital NOK 104,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−241k kr).
  • Nylig endring 2026-05-13 Adresseendring registrert 2026-05-13.

SLOTTSKAKER AS is registered as a limited company in Åmli, Agder with organisation number 989051849. The business is classified under manufacture of bread; manufacture of fresh pastry goods and cakes (NACE 10.710). The company was incorporated in 2005. Registered share capital is NOK 104,000, divided into 104 shares. The company's stated purpose is: “Selskapets virksomhet er å eie fast eiendom, eiendomsutvikling og utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −241,000
Equity
NOK 4.4m
Est. value
NOK 5.2m

Financial health · 2025

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

Who owns SLOTTSKAKER AS?

ESPEN MYHREN
SLOTTSKAKER AS
· NOK −241,000 profit

SLOTTSKAKER AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SLOTTSKAKER AS own?

SLOTTSKAKER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SLOTTSKAKER AS

Who owns SLOTTSKAKER AS?

ESPEN MYHREN is the largest registered owner, with 96.2%.

Who is the general manager of SLOTTSKAKER AS?

Espen Myhren is registered as general manager of SLOTTSKAKER AS.

Where is SLOTTSKAKER AS based?

SLOTTSKAKER AS has its business address in Åmli.

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.