BIZTRAC BETA
Rental and operating of own or leased real estate

SLYNGA 10 AS

Org. no. 915713734 Limited company (AS) Nordre Follo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 1.6m
Equity NOK 2.5m
Incorporated 2015
Share capital NOK 33,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SLYNGA 10 AS is registered as a limited company in Nordre Follo, Akershus with organisation number 915713734. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 33,000, divided into 300 shares. The company's stated purpose is: “Handel, utvikling, kjøp, salg og utleie av fast eiendom, samt annen virksomhet som naturlig faller inn under dette ved aksjekjøp eller annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 1.6m
Equity
NOK 2.5m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns SLYNGA 10 AS?

BEE AS
SLYNGA 10 AS
NOK 3.8m rev. · NOK 1.6m profit

SLYNGA 10 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SLYNGA 10 AS

Who owns SLYNGA 10 AS?

BEE AS is the largest registered owner, with 100.0%.

What is the revenue of SLYNGA 10 AS?

SLYNGA 10 AS had revenue of NOK 3.8m in 2024.

Who is the general manager of SLYNGA 10 AS?

Joachim Graff is registered as general manager of SLYNGA 10 AS.

Where is SLYNGA 10 AS based?

SLYNGA 10 AS has its business address in Ski.

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.