BIZTRAC BETA
Other performing arts activities

PØLSA AS

Org. no. 923743685 Limited company (AS) Lillehammer Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 4.5m
Equity NOK 14.7m
Incorporated 2019
Share capital NOK 30,000

PØLSA AS is registered as a limited company in Lillehammer, Innlandet with organisation number 923743685. The business is classified under other performing arts activities (NACE 90.209). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Foredragsvirksomhet, konsulenttjenester og konferansièr. Alt under tema som omhandler bevissthet rundt prestasjon, utvikling og resultater. Skikurs/teknikk. Investeringer/plassering av overskuddslikviditet, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 4.5m in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
Operating profit
NOK 4.5m
Equity
NOK 14.7m
Est. value
NOK 22.4m

Financial health · 2025

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

Who owns PØLSA AS?

ØYSTEIN PETTERSEN
PØLSA AS
NOK 6.1m rev. · NOK 4.5m profit

PØLSA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PØLSA AS own?

PØLSA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PØLSA AS

Who owns PØLSA AS?

ØYSTEIN PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of PØLSA AS?

PØLSA AS had revenue of NOK 6.1m in 2025.

Who is the general manager of PØLSA AS?

Øystein Pettersen is registered as general manager of PØLSA AS.

Where is PØLSA AS based?

PØLSA AS has its business address in Lillehammer.

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.