BIZTRAC BETA
Other performing arts activities

PINNE PÅ NESA AS

Org. no. 832111422 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 184,000
Operating profit NOK −4,000
Equity NOK 57,000
Incorporated 2023
Share capital NOK 60,000

Signals

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

PINNE PÅ NESA AS is registered as a limited company in Drammen, Buskerud with organisation number 832111422. The business is classified under other performing arts activities (NACE 90.209). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Produksjon av forestillinger og annen scenisk og kunstnerisk virksomhet, drift av kulturtjenester samt salg av rettigheter og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 184,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 184,000
Operating profit
NOK −4,000
Equity
NOK 57,000
Est. value
NOK 210,000

Financial health · 2025

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

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

Who owns PINNE PÅ NESA AS?

KIM PETER HENSCHIEN HOLTAN
PINNE PÅ NESA AS
NOK 184,000 rev. · NOK −4,000 profit

PINNE PÅ NESA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PINNE PÅ NESA AS

Who owns PINNE PÅ NESA AS?

KIM PETER HENSCHIEN HOLTAN is the largest registered owner, with 33.3%.

What is the revenue of PINNE PÅ NESA AS?

PINNE PÅ NESA AS had revenue of NOK 184,000 in 2025.

Where is PINNE PÅ NESA AS based?

PINNE PÅ NESA AS has its business address in Drammen.

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.