BIZTRAC BETA
Computer programming activities

SHADCODING AS

Org. no. 927549891 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 515,000
Equity NOK 442,000
Incorporated 2021
Share capital NOK 30,000

SHADCODING AS is registered as a limited company in Oslo, Oslo with organisation number 927549891. 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 100 shares. The company's stated purpose is: “Utvikle, produsere, selge og levere IT-tjenester og -produkter, inkludert, men ikke begrenset til, programvareutvikling, IT-konsulenttjenester, IT-drift og vedlikehold, skytjenester, nettverksløsninger, datalagring, IT-sikkerhet og andre tjenester og produkter relatert til informasjonsteknologi. Selskapet kan også investere i andre virksomheter, samt drive annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 515,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 515,000
Equity
NOK 442,000
Est. value
NOK 2.4m

Financial health · 2024

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.2%
Good
Equity as a share of total capital

Who owns SHADCODING AS?

ISTARLIN MOHAMED ISSAK
SHADCODING AS
NOK 1.6m rev. · NOK 515,000 profit

SHADCODING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SHADCODING AS

Who owns SHADCODING AS?

ISTARLIN MOHAMED ISSAK is the largest registered owner, with 100.0%.

What is the revenue of SHADCODING AS?

SHADCODING AS had revenue of NOK 1.6m in 2024.

Where is SHADCODING AS based?

SHADCODING 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 15.06.2026.

Report a problem

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