BIZTRAC BETA
Computer programming activities

PUN AS

Org. no. 932127555 Limited company (AS) Tromsø Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 9,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

PUN AS is registered as a limited company in Tromsø, Troms with organisation number 932127555. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Skal selge varer og tjenester innen programmering, 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 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 9,000
Est. value
NOK 16,000

Financial health · 2025

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

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

Who owns PUN AS?

STIAN HANSSEN
PUN AS
NOK 0 rev. · NOK −7,000 profit

PUN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PUN AS own?

PUN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PUN AS

Who owns PUN AS?

STIAN HANSSEN is the largest registered owner, with 100.0%.

What is the revenue of PUN AS?

PUN AS had revenue of NOK 0 in 2025.

Who is the general manager of PUN AS?

Stian Hanssen is registered as general manager of PUN AS.

Where is PUN AS based?

PUN AS has its business address in Tromsø.

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.