BIZTRAC BETA
COMPANY REGISTER PROFILE
932894777 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SØBERG CONSULTING AS

Org. no. 932894777 Limited company (AS) Eidsvoll Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK 170,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

SØBERG CONSULTING AS is registered as a limited company in Eidsvoll, Akershus with organisation number 932894777. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i verdipapirer og andre formuesobjekter.”.

Key figures · 2025

Operating profit
NOK −15,000
Equity
NOK 170,000
Est. value
NOK 200,000

Financial health · 2025

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

Who owns SØBERG CONSULTING AS?

SØBERG CONSULTING AS
· NOK −15,000 profit

SØBERG CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØBERG CONSULTING AS

Who owns SØBERG CONSULTING AS?

PETTER SØBERG is the largest registered owner, with 100.0%.

Where is SØBERG CONSULTING AS based?

SØBERG CONSULTING AS has its business address in Eidsvoll.

Property

Business address c/o Petter Søberg Åsleia 181, 2080 Eidsvoll
Cadastral unit 3240-162/1/0/0
Building Våningshus · 1 unit

3 companies are registered at this address.

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.