BIZTRAC BETA
Computer programming activities

PAYRUN AS

Org. no. 816694272 Limited company (AS) Lillestrøm Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 200,000
Operating profit NOK −2.7m
Equity NOK −2.7m
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,7 mill kr).

PAYRUN AS is registered as a limited company in Lillestrøm, Akershus with organisation number 816694272. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000000 shares. The company's stated purpose is: “Utvikling, produksjon, leie og salg av programvare, handel- og konsulentvirksomhet, tjenesteyting og all annen tilknyttet og beslektet økonomisk virksomhet, samt deltagelse i andre virksomheter og selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 200,000 in revenue and NOK −2.7m in operating profit.

Key figures · 2024

Revenue
NOK 200,000
Operating profit
NOK −2.7m
Equity
NOK −2.7m

Financial health · 2024

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2215.6%
Weak
Equity as a share of total capital

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

Who owns PAYRUN AS?

GAIN SOLUTIONS AS
PAYRUN AS
NOK 200,000 rev. · NOK −2.7m profit

PAYRUN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PAYRUN AS

Who owns PAYRUN AS?

GAIN SOLUTIONS AS is the largest registered owner, with 100.0%.

What is the revenue of PAYRUN AS?

PAYRUN AS had revenue of NOK 200,000 in 2024.

Where is PAYRUN AS based?

PAYRUN AS has its business address in Lillestrøm.

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.