BIZTRAC BETA
COMPANY REGISTER PROFILE
935906555 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Motion picture, video and television programme production activities

HUMLEKJÆR AS

Org. no. 935906555 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −91,000
Equity NOK −68,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

HUMLEKJÆR AS is registered as a limited company in Oslo, Oslo with organisation number 935906555. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen utleie av eiendom - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures · 2025

Operating profit
NOK −91,000
Equity
NOK −68,000

Financial health · 2025

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

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

Who owns HUMLEKJÆR AS?

KRISTOFFER ANDRE HUMLEKJÆR
HUMLEKJÆR AS
· NOK −91,000 profit

HUMLEKJÆR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUMLEKJÆR AS

Who owns HUMLEKJÆR AS?

KRISTOFFER ANDRE HUMLEKJÆR is the largest registered owner, with 100.0%.

Who is the general manager of HUMLEKJÆR AS?

Kristoffer Andre Humlekjær is registered as general manager of HUMLEKJÆR AS.

Where is HUMLEKJÆR AS based?

HUMLEKJÆR 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.