BIZTRAC BETA
COMPANY REGISTER PROFILE
935100488 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

PK REFSETH HOLDING AS

Org. no. 935100488 Limited company (AS) Midtre Gauldal Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-23 Adresseendring registrert 2026-05-23.

PK REFSETH HOLDING AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 935100488. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med investering i aksjer og verdipapirer, inkludert, men ikke begrenset til, kjøp, salg og forvaltning av aksjer, obligasjoner, derivater og andre finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns PK REFSETH HOLDING AS?

PK REFSETH HOLDING AS
NOK 0 rev. · NOK 0 profit

PK REFSETH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PK REFSETH HOLDING AS

Who owns PK REFSETH HOLDING AS?

PER KRISTIAN REFSETH is the largest registered owner, with 100.0%.

What is the revenue of PK REFSETH HOLDING AS?

PK REFSETH HOLDING AS had revenue of NOK 0 in 2025.

Where is PK REFSETH HOLDING AS based?

PK REFSETH HOLDING AS has its business address in Støren.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.