biztrac. BETA
COMPANY REGISTER PROFILE
933696634 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Manufacture of bread; manufacture of fresh pastry goods and cakes

FISK & BRØD AS

Org. no. 933696634 Limited company (AS) Askøy Incorporated 2024 Active
Operating profit NOK −18,000
Equity NOK 49,000
Incorporated 2024
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

FISK & BRØD AS is registered as a limited company in Askøy, Vestland with organisation number 933696634. The business is classified under manufacture of bread; manufacture of fresh pastry goods and cakes (NACE 10.710). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Er å eie aksjer og andeler i andre virksomheter, samt hva hermed står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −18,000
▲ +35 %
Equity
NOK 49,000
▼ −26 %
Est. value
NOK 58,000

Financial health · 2025

Liquidity
0.52
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
31.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FISK & BRØD AS?

FISK & BRØD AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FISK & BRØD AS own?

FISK & BRØD AS holds a stake in 1 company:

See the full ownership structure →

Group structure

FISK & BRØD AS er morselskap for 1 datterselskap:

Frequently asked questions about FISK & BRØD AS

Who owns FISK & BRØD AS?

Gun Monica Mannelqvist is the largest registered owner, with 50.0%.

Who is the general manager of FISK & BRØD AS?

Jan Arne Brekke is registered as general manager of FISK & BRØD AS.

Where is FISK & BRØD AS based?

FISK & BRØD AS has its business address in Follese.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.