BIZTRAC BETA
COMPANY REGISTER PROFILE
925793353 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

MEME SHAKE AS

Org. no. 925793353 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2023 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.
  • Nylig endring 2026-06-22 Under avvikling registrert 2026-06-22.

MEME SHAKE AS is registered as a limited company in Oslo, Oslo with organisation number 925793353. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling, forskning, produksjon, administrasjon, salg og distribusjon innen bransjene teknologi, media, nyheter, film, musikk, konferanser og eventer/live underholdning, samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2023 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2023

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 54,000

Financial health · 2023

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 MEME SHAKE AS?

No shareholders are registered for MEME SHAKE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MEME SHAKE AS

What is the revenue of MEME SHAKE AS?

MEME SHAKE AS had revenue of NOK 0 in 2023.

Where is MEME SHAKE AS based?

MEME SHAKE 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.