BIZTRAC BETA
Performing arts activities in dramatic arts

PER KJERSTAD AS

Org. no. 926666096 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 642,000
Equity NOK 557,000
Incorporated 2021
Share capital NOK 30,000

PER KJERSTAD AS is registered as a limited company in Stavanger, Rogaland with organisation number 926666096. The business is classified under performing arts activities in dramatic arts (NACE 90.202). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produksjon og formidling av utøvende kunstnerisk virksomhet, holde foredrag samt investeringsvirksomhet og alt som naturlig hører med.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 642,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 642,000
Equity
NOK 557,000
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
0.63
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.2%
Good
Equity as a share of total capital

Who owns PER KJERSTAD AS?

PER KJERSTAD
PER KJERSTAD AS
NOK 2.8m rev. · NOK 642,000 profit

PER KJERSTAD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PER KJERSTAD AS own?

PER KJERSTAD AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about PER KJERSTAD AS

Who owns PER KJERSTAD AS?

PER KJERSTAD is the largest registered owner, with 100.0%.

What is the revenue of PER KJERSTAD AS?

PER KJERSTAD AS had revenue of NOK 2.8m in 2025.

Who is the general manager of PER KJERSTAD AS?

Per Kjerstad is registered as general manager of PER KJERSTAD AS.

Where is PER KJERSTAD AS based?

PER KJERSTAD AS has its business address in Stavanger.

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.