BIZTRAC BETA
COMPANY REGISTER PROFILE
935969409 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Retail sale of sports equipment

SKYTTERN AS

Org. no. 935969409 Limited company (AS) Lillestrøm Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK 3,000
Equity NOK 32,000
Incorporated 2025
Share capital NOK 30,000

SKYTTERN AS is registered as a limited company in Lillestrøm, Akershus with organisation number 935969409. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Netthandel. Salg av klær og utstyr.”.

Key figures · 2025

Operating profit
NOK 3,000
Equity
NOK 32,000
Est. value
NOK 26,000

Financial health · 2025

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

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

Who owns SKYTTERN AS?

SKYTTERN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKYTTERN AS

Who owns SKYTTERN AS?

ADCO HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of SKYTTERN AS?

Ronny Licina Steng is registered as general manager of SKYTTERN AS.

Where is SKYTTERN AS based?

SKYTTERN AS has its business address in Frogner.

Property

Business address Trollsvingen 11, 2016 Frogner
Cadastral unit 3205-282/73/0/0
Building Enebolig · 1 unit

4 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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