BIZTRAC BETA
Computer programming activities

SY MARKETING AS

Org. no. 927972468 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 1.9m
Equity NOK 1.5m
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-14 Adresseendring registrert 2026-02-14.

SY MARKETING AS is registered as a limited company in Bergen, Vestland with organisation number 927972468. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen programmeringstjenester, IT-konsultasjon, markedsføring på nett og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 1.9m
Equity
NOK 1.5m
Est. value
NOK 6.8m

Financial health · 2025

Liquidity
2.01
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.2%
Very good
Equity as a share of total capital

Who owns SY MARKETING AS?

SAID YASAEV
SY MARKETING AS
NOK 3.5m rev. · NOK 1.9m profit

SY MARKETING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SY MARKETING AS

Who owns SY MARKETING AS?

SAID YASAEV is the largest registered owner, with 100.0%.

What is the revenue of SY MARKETING AS?

SY MARKETING AS had revenue of NOK 3.5m in 2025.

Who is the general manager of SY MARKETING AS?

Said Yasaev is registered as general manager of SY MARKETING AS.

Where is SY MARKETING AS based?

SY MARKETING AS has its business address in Bergen.

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.