biztrac. BETA
COMPANY REGISTER PROFILE
935219655 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Sound recording and music publishing activities

HIMMELSKIP AS

Org. no. 935219655 Limited company (AS) Oslo Incorporated 2025 Active
Revenue 2025 NOK 156,000
Operating profit NOK 34,000
Equity NOK 76,000
Incorporated 2025
Share capital NOK 30,000

HIMMELSKIP AS is registered as a limited company in Oslo, Oslo with organisation number 935219655. The business is classified under sound recording and music publishing activities (NACE 59.200). 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 produksjon av musikk - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 156,000 in revenue and NOK 34,000 in operating profit.

Key figures · 2025

Revenue
NOK 156,000
Operating profit
NOK 34,000
Equity
NOK 76,000
Est. value
NOK 232,000

Financial health · 2025

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

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

Who owns HIMMELSKIP AS?

HIMMELSKIP AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about HIMMELSKIP AS

Who owns HIMMELSKIP AS?

Simen Jakobsen Harstad is the largest registered owner, with 25.0%.

What is the revenue of HIMMELSKIP AS?

HIMMELSKIP AS had revenue of NOK 156,000 in 2025.

Who is the general manager of HIMMELSKIP AS?

Elias Wallumrød Orning is registered as general manager of HIMMELSKIP AS.

Where is HIMMELSKIP AS based?

HIMMELSKIP 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 03.10.2026.

Report a problem

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