BIZTRAC BETA
Computer programming activities

PEPLING AS

Org. no. 994769146 Limited company (AS) Hamar Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 23,000
Operating profit NOK −15,000
Equity NOK 4.0m
Incorporated 2009
Share capital NOK 150,000

Signals

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

PEPLING AS is registered as a limited company in Hamar, Innlandet with organisation number 994769146. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2009. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er konsultent og rådgivning innen software, samt deltagelse i relaterte virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 23,000 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 23,000
Operating profit
NOK −15,000
Equity
NOK 4.0m
Est. value
NOK 12.9m

Financial health · 2025

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

Who owns PEPLING AS?

STIG ANDRÉ PETERSHEIM
PEPLING AS
NOK 23,000 rev. · NOK −15,000 profit

PEPLING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PEPLING AS own?

PEPLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PEPLING AS

Who owns PEPLING AS?

STIG ANDRÉ PETERSHEIM is the largest registered owner, with 100.0%.

What is the revenue of PEPLING AS?

PEPLING AS had revenue of NOK 23,000 in 2025.

Who is the general manager of PEPLING AS?

Stig André Petersheim is registered as general manager of PEPLING AS.

Where is PEPLING AS based?

PEPLING AS has its business address in Hamar.

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.