BIZTRAC BETA
COMPANY REGISTER PROFILE
999292704 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

PK KONSULENTEN PETTER KVAAL

Org. no. 999292704 Sole proprietorship (ENK) Bærum Active
Ownership graph ↗
Revenue 2025 NOK 26,000
Operating profit NOK 12,000
Equity NOK 12,000

PK KONSULENTEN PETTER KVAAL is registered as a sole proprietorship in Bærum, Akershus with organisation number 999292704. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The most recent filed accounts, for the 2025 financial year, show NOK 26,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 26,000
Operating profit
NOK 12,000
Equity
NOK 12,000
Est. value
NOK 40,000

Financial health · 2025

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

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

Who owns PK KONSULENTEN PETTER KVAAL?

No shareholders are registered for PK KONSULENTEN PETTER KVAAL in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about PK KONSULENTEN PETTER KVAAL

What is the revenue of PK KONSULENTEN PETTER KVAAL?

PK KONSULENTEN PETTER KVAAL had revenue of NOK 26,000 in 2025.

Where is PK KONSULENTEN PETTER KVAAL based?

PK KONSULENTEN PETTER KVAAL has its business address in Slependen.

Property

Business address Tanumveien 54C, 1341 Slependen
Cadastral unit 3201-119/76/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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