BIZTRAC BETA
Event catering activities

SUK-SAN AS

Org. no. 915000967 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 8.3m
Operating profit NOK 169,000
Equity NOK −172,000
Incorporated 2015
Employees 9
Share capital NOK 30,000

Signals

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

SUK-SAN AS is registered as a limited company in Oslo, Oslo with organisation number 915000967. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2015 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Omsetning av mat og drikke gjennom butikk- og restaurantvirksomhet, herunder catering, og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.3m in revenue and NOK 169,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.3m
Operating profit
NOK 169,000
Equity
NOK −172,000
Est. value
NOK 1.3m

Financial health · 2024

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

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

Who owns SUK-SAN AS?

PRATTHANA SILAPORN
SUK-SAN AS
NOK 8.3m rev. · NOK 169,000 profit

SUK-SAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SUK-SAN AS

Who owns SUK-SAN AS?

PRATTHANA SILAPORN is the largest registered owner, with 100.0%.

What is the revenue of SUK-SAN AS?

SUK-SAN AS had revenue of NOK 8.3m in 2024.

Who is the general manager of SUK-SAN AS?

Kim Lauge Helmuth Larsen is registered as general manager of SUK-SAN AS.

Where is SUK-SAN AS based?

SUK-SAN AS has its business address in Oslo.

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.