BIZTRAC BETA
Restaurant activities

SIAM AS

Org. no. 922760403 Limited company (AS) Fredrikstad Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 11,000
Equity NOK −610,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−610k kr).

SIAM AS is registered as a limited company in Fredrikstad, Østfold with organisation number 922760403. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Serveringsvirksomhet, take-away samt kulturarrangement og annet som naturlig faller sammen med dette. For øvrig skal selskapet kunne delta i alle beslektede aktiviteter, herunder kjøp og salg av andre selskaper og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 11,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 11,000
Equity
NOK −610,000
Est. value
NOK 53,000

Financial health · 2023

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-250.0%
Weak
Equity as a share of total capital

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

Who owns SIAM AS?

RUNGTAWAN RUNGRUEANG
SIAM AS
NOK 3.7m rev. · NOK 11,000 profit

SIAM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIAM AS

Who owns SIAM AS?

RUNGTAWAN RUNGRUEANG is the largest registered owner, with 50.0%.

What is the revenue of SIAM AS?

SIAM AS had revenue of NOK 3.7m in 2024.

Who is the general manager of SIAM AS?

Tore Fred Omberg is registered as general manager of SIAM AS.

Where is SIAM AS based?

SIAM 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 15.06.2026.

Report a problem

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