BIZTRAC BETA
Motion picture, video and television programme production activities

NOE Å SI AS

Org. no. 935576172 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 36,000
Operating profit NOK 25,000
Equity NOK 44,000
Incorporated 2025
Share capital NOK 30,000

NOE Å SI AS is registered as a limited company in Oslo, Oslo with organisation number 935576172. 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 filmproduksjon - 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 36,000 in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 36,000
Operating profit
NOK 25,000
Equity
NOK 44,000
Est. value
NOK 110,000

Financial health · 2025

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

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

Who owns NOE Å SI AS?

JOACHIM FOSS RØNNING
NOE Å SI AS
NOK 36,000 rev. · NOK 25,000 profit

NOE Å SI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NOE Å SI AS

Who owns NOE Å SI AS?

JOACHIM FOSS RØNNING is the largest registered owner, with 100.0%.

What is the revenue of NOE Å SI AS?

NOE Å SI AS had revenue of NOK 36,000 in 2025.

Who is the general manager of NOE Å SI AS?

Joachim Foss Rønning is registered as general manager of NOE Å SI AS.

Where is NOE Å SI AS based?

NOE Å SI 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.