BIZTRAC BETA
Computer consultancy and computer facilities management activities

MPEDERSEN CONSULTING AS

Org. no. 929425065 Limited company (AS) Vestby Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 1.3m
Equity NOK 118,000
Incorporated 2022
Share capital NOK 30,000

MPEDERSEN CONSULTING AS is registered as a limited company in Vestby, Akershus with organisation number 929425065. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Utleie av konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 1.3m
Equity
NOK 118,000
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns MPEDERSEN CONSULTING AS?

MPEDERSEN HOLDING AS
MPEDERSEN CONSULTING AS
NOK 2.9m rev. · NOK 1.3m profit

MPEDERSEN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MPEDERSEN CONSULTING AS er morselskap for 1 datterselskap:

Frequently asked questions about MPEDERSEN CONSULTING AS

Who owns MPEDERSEN CONSULTING AS?

MPEDERSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MPEDERSEN CONSULTING AS?

MPEDERSEN CONSULTING AS had revenue of NOK 2.9m in 2025.

Who is the general manager of MPEDERSEN CONSULTING AS?

Marius Pedersen is registered as general manager of MPEDERSEN CONSULTING AS.

Where is MPEDERSEN CONSULTING AS based?

MPEDERSEN CONSULTING AS has its business address in Son.

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.