BIZTRAC BETA
COMPANY REGISTER PROFILE
930908274 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

JEEY AS

Org. no. 930908274 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Equity NOK 22,000
Incorporated 2023
Share capital NOK 30,000

JEEY AS is registered as a limited company in Oslo, Oslo with organisation number 930908274. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere i selskaper og eiendom, samt andre aktiviteter knyttet til kjøp og salg av aksjer.”.

Key figures · 2025

Equity
NOK 22,000
Est. value
NOK 12,000

Financial health · 2025

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

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

Who owns JEEY AS?

JEEY AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JEEY AS own?

JEEY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JEEY AS

Who owns JEEY AS?

SANEL ZEJNELAGIC is the largest registered owner, with 50.0%.

Who is the general manager of JEEY AS?

Karima El Barkani is registered as general manager of JEEY AS.

Where is JEEY AS based?

JEEY AS has its business address in Oslo.

Property

Business address Sloreåsen 50A, 1257 Oslo
Cadastral unit 301-194/777/0/0
Building Rekkehus · 1 unit

2 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.