biztrac. BETA
COMPANY REGISTER PROFILE
926102397 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other non-specialised retail sale

KRASNASHOPP.COM AS

Org. no. 926102397 Limited company (AS) Haugesund Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 23
Operating profit NOK −11,000
Equity NOK −115,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−115k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

KRASNASHOPP.COM AS is registered as a limited company in Haugesund, Rogaland with organisation number 926102397. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Online produktsalg.”. The most recent filed accounts, for the 2025 financial year, show NOK 23 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 23
▼ −100 %
Operating profit
NOK −11,000
▲ +67 %
Equity
NOK −115,000
▼ −10 %

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
-249.2%
Not satisfactory
Return on total assets
Solidity
-1817.0%
Weak
Equity as a share of total capital

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

Who owns KRASNASHOPP.COM AS?

KRASNASHOPP.COM AS
NOK 23 rev. · NOK −11,000 profit

KRASNASHOPP.COM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRASNASHOPP.COM AS

Who owns KRASNASHOPP.COM AS?

KRASNIQ TEAM AS is the largest registered owner, with 100.0%.

What is the revenue of KRASNASHOPP.COM AS?

KRASNASHOPP.COM AS had revenue of NOK 23 in 2025.

Where is KRASNASHOPP.COM AS based?

KRASNASHOPP.COM AS has its business address in Haugesund.

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

Report a problem

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