BIZTRAC BETA
Uoppgitt

ERRING HOLDING AS

Org. no. 928986713 Limited company (AS) Moss Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK −17,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−17k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

ERRING HOLDING AS is registered as a limited company in Moss, Østfold with organisation number 928986713. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i aksjer og eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK −17,000

Financial health · 2025

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

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

Who owns ERRING HOLDING AS?

THOMAS ERRING HANSEN
ERRING HOLDING AS
NOK 0 rev. · NOK −16,000 profit

ERRING HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERRING HOLDING AS own?

ERRING HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ERRING HOLDING AS

Who owns ERRING HOLDING AS?

THOMAS ERRING HANSEN is the largest registered owner, with 100.0%.

What is the revenue of ERRING HOLDING AS?

ERRING HOLDING AS had revenue of NOK 0 in 2025.

Where is ERRING HOLDING AS based?

ERRING HOLDING AS has its business address in Moss.

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.