BIZTRAC BETA
Uoppgitt

PEKE HOLDING AS

Org. no. 924449829 Limited company (AS) Lier Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 45,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

PEKE HOLDING AS is registered as a limited company in Lier, Buskerud with organisation number 924449829. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap. Investering i aksjer og øvrige verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 45,000
Est. value
NOK 54,000

Financial health · 2025

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

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

Who owns PEKE HOLDING AS?

PER ERIK KIRKAUNE
PEKE HOLDING AS
NOK 0 rev. · NOK −14,000 profit

PEKE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PEKE HOLDING AS own?

PEKE HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PEKE HOLDING AS

Who owns PEKE HOLDING AS?

PER ERIK KIRKAUNE is the largest registered owner, with 100.0%.

What is the revenue of PEKE HOLDING AS?

PEKE HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of PEKE HOLDING AS?

Per Erik Kirkaune is registered as general manager of PEKE HOLDING AS.

Where is PEKE HOLDING AS based?

PEKE HOLDING AS has its business address in Gullaug.

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.