biztrac. BETA
COMPANY REGISTER PROFILE
919018801 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

DROLSHAMMER AS

Org. no. 919018801 Limited company (AS) Moss Incorporated 2017 Active
Operating profit NOK −194
Equity NOK 250,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

DROLSHAMMER AS is registered as a limited company in Moss, Østfold with organisation number 919018801. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester innen informasjonsteknologi, samt drift og utvikling av egne og andre selskapers digitale løsninger, investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper, samt kjøp, salg og utleie av fast eiendom og annet som naturlig faller sammen med dette.”.

Key figures · 2025

Operating profit
NOK −194
▲ +98 %
Equity
NOK 250,000
▼ −38 %
Est. value
NOK 453,000

Financial health · 2025

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

Who owns DROLSHAMMER AS?

DROLSHAMMER AS
· NOK −194 profit

DROLSHAMMER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DROLSHAMMER AS own?

DROLSHAMMER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DROLSHAMMER AS

Who owns DROLSHAMMER AS?

Erik Drolshammer is the largest registered owner, with 100.0%.

Where is DROLSHAMMER AS based?

DROLSHAMMER 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 03.10.2026.

Report a problem

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