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

LOADOUT AS

Org. no. 933849619 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK 9,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

LOADOUT AS is registered as a limited company in Oslo, Oslo with organisation number 933849619. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Design. Programmering, salg, drift og utvikling av digitale løsninger, samt forbunden virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK 9,000
Est. value
NOK 16,000

Financial health · 2025

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

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

Who owns LOADOUT AS?

JULIAN TOBIAS LUNDGREN
LOADOUT AS
NOK 0 rev. · NOK −11,000 profit

LOADOUT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOADOUT AS

Who owns LOADOUT AS?

JULIAN TOBIAS LUNDGREN is the largest registered owner, with 100.0%.

What is the revenue of LOADOUT AS?

LOADOUT AS had revenue of NOK 0 in 2025.

Who is the general manager of LOADOUT AS?

Julian Tobias Lundgren is registered as general manager of LOADOUT AS.

Where is LOADOUT AS based?

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