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

SYNG AS

Org. no. 997307399 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 13.9m
Operating profit NOK −2.0m
Equity NOK 1.3m
Incorporated 2011
Employees 35
Share capital NOK 143,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,0 mill kr).

SYNG AS is registered as a limited company in Oslo, Oslo with organisation number 997307399. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2011 and has 35 registered employees. Registered share capital is NOK 143,000, divided into 142857 shares. The company's stated purpose is: “Servering og sang samt generell investering, herunder investering i aksjer og deltagelse i andre selskaper og andre disposisjoner i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.9m in revenue and NOK −2.0m in operating profit.

Key figures · 2025

Revenue
NOK 13.9m
▼ −6 %
Operating profit
NOK −2.0m
▼ −154 %
Equity
NOK 1.3m
▼ −61 %
Est. value
NOK 10.2m

Financial health · 2025

Liquidity
0.73
Weak
Current assets ÷ current liabilities
Profitability
-43.9%
Not satisfactory
Return on total assets
Solidity
35.7%
Good
Equity as a share of total capital

Who owns SYNG AS?

SYNG AS
NOK 13.9m rev. · NOK −2.0m profit

SYNG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYNG AS

Who owns SYNG AS?

SYNG OVERALT AS is the largest registered owner, with 100.0%.

What is the revenue of SYNG AS?

SYNG AS had revenue of NOK 13.9m in 2025.

Who is the general manager of SYNG AS?

Ida Sigurdsen is registered as general manager of SYNG AS.

Where is SYNG AS based?

SYNG 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 03.10.2026.

Report a problem

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