BIZTRAC BETA
COMPANY REGISTER PROFILE
834384612 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

PELA CONSULTING AS

Org. no. 834384612 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 240,000
Operating profit NOK 220,000
Equity NOK 244,000
Incorporated 2024
Share capital NOK 30,000

PELA CONSULTING AS is registered as a limited company in Oslo, Oslo with organisation number 834384612. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulenttjenester innen salg, salgsledelse, strategi og markedsføring.”. The most recent filed accounts, for the 2024 financial year, show NOK 240,000 in revenue and NOK 220,000 in operating profit.

Key figures · 2024

Revenue
NOK 240,000
Operating profit
NOK 220,000
Equity
NOK 244,000
Est. value
NOK 861,000

Financial health · 2024

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

Who owns PELA CONSULTING AS?

PETTER HEIER LARSEN
PELA CONSULTING AS
NOK 240,000 rev. · NOK 220,000 profit

PELA CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PELA CONSULTING AS

Who owns PELA CONSULTING AS?

PETTER HEIER LARSEN is the largest registered owner, with 100.0%.

What is the revenue of PELA CONSULTING AS?

PELA CONSULTING AS had revenue of NOK 240,000 in 2024.

Who is the general manager of PELA CONSULTING AS?

Petter Heier Larsen is registered as general manager of PELA CONSULTING AS.

Where is PELA CONSULTING AS based?

PELA CONSULTING AS has its business address in Oslo.

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.