biztrac. BETA
COMPANY REGISTER PROFILE
935151945 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

NOBERG HOLDING AS

Org. no. 935151945 Limited company (AS) Ullensaker Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK 7
Equity NOK 43,000
Incorporated 2025
Share capital NOK 50,000

NOBERG HOLDING AS is registered as a limited company in Ullensaker, Akershus with organisation number 935151945. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Investeringer i fast eiendom og aksjer, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 7 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 7
Equity
NOK 43,000
Est. value
NOK 23,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 NOBERG HOLDING AS?

NOBERG HOLDING AS
NOK 0 rev. · NOK 7 profit

NOBERG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NOBERG HOLDING AS own?

NOBERG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NOBERG HOLDING AS

Who owns NOBERG HOLDING AS?

Magne Bergersen is the largest registered owner, with 100.0%.

What is the revenue of NOBERG HOLDING AS?

NOBERG HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of NOBERG HOLDING AS?

Magne Bergersen is registered as general manager of NOBERG HOLDING AS.

Where is NOBERG HOLDING AS based?

NOBERG HOLDING AS has its business address in Jessheim.

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

Report a problem

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