biztrac. BETA
COMPANY REGISTER PROFILE
834385082 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of games and toys

LOGINN AS

Org. no. 834385082 Limited company (AS) Ringsaker Incorporated 2024 Active
Revenue 2025 NOK 11,000
Operating profit NOK −20,000
Equity NOK 9,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−20k kr).

LOGINN AS is registered as a limited company in Ringsaker, Innlandet with organisation number 834385082. The business is classified under retail sale of games and toys (NACE 47.640). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive netthandel med klær, sko og utstyrsvarer, inkludert salg og distribusjon gjennom digitale plattformer. Drive med konsultasjoner og kurs i logistikk og ledelse gjennom digitale plattformer og fysiske møter.”. The most recent filed accounts, for the 2025 financial year, show NOK 11,000 in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 11,000
Operating profit
NOK −20,000
▼ −1211 %
Equity
NOK 9,000
▼ −69 %
Est. value
NOK 8,000

Financial health · 2025

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

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

Who owns LOGINN AS?

LOGINN AS
NOK 11,000 rev. · NOK −20,000 profit

LOGINN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOGINN AS

Who owns LOGINN AS?

Mariusz Rafal Gruda is the largest registered owner, with 50.0%.

What is the revenue of LOGINN AS?

LOGINN AS had revenue of NOK 11,000 in 2025.

Where is LOGINN AS based?

LOGINN AS has its business address in Furnes.

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.