biztrac. BETA
COMPANY REGISTER PROFILE
829035502 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

BAHA FREDRIKSTAD AS

Org. no. 829035502 Limited company (AS) Fredrikstad Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK −190,000
Incorporated 2022
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−190k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

BAHA FREDRIKSTAD AS is registered as a limited company in Fredrikstad, Østfold with organisation number 829035502. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Drift av café. restaurant og bar. servering av mat og drikke, underholdning, samt import. engroshandel, distrbusjon og salg av næringsmidler og annen virksomhet som naturlig hører sammen dette.”.

Key figures · 2025

Operating profit
NOK −4,000
▲ +29 %
Equity
NOK −190,000
▼ −2 %

Financial health · 2025

Liquidity
-27.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
2.4%
Weak
Return on total assets
Solidity
103.6%
Weak
Equity as a share of total capital

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

Who owns BAHA FREDRIKSTAD AS?

BAHA FREDRIKSTAD AS
· NOK −4,000 profit

BAHA FREDRIKSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BAHA FREDRIKSTAD AS

Who owns BAHA FREDRIKSTAD AS?

Bahareh Letnes is the largest registered owner, with 100.0%.

Who is the general manager of BAHA FREDRIKSTAD AS?

Bahareh Letnes is registered as general manager of BAHA FREDRIKSTAD AS.

Where is BAHA FREDRIKSTAD AS based?

BAHA FREDRIKSTAD AS has its business address in Fredrikstad.

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.