biztrac. BETA
COMPANY REGISTER PROFILE
919910143 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

HAMMER MOEN HOLDING AS

Org. no. 919910143 Limited company (AS) Stryn Incorporated 2017 Active
Operating profit NOK −8,000
Equity NOK −121,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−121k kr).

HAMMER MOEN HOLDING AS is registered as a limited company in Stryn, Vestland with organisation number 919910143. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å eie datterselskap innen ulike bransjer, investeringer herunder kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre fortagender.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −16 %
Equity
NOK −121,000
▼ −809 %

Financial health · 2025

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

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

Who owns HAMMER MOEN HOLDING AS?

HAMMER MOEN HOLDING AS
· NOK −8,000 profit

HAMMER MOEN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HAMMER MOEN HOLDING AS own?

HAMMER MOEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HAMMER MOEN HOLDING AS

Who owns HAMMER MOEN HOLDING AS?

John Bjørn Moen is the largest registered owner, with 50.0%.

Who is the general manager of HAMMER MOEN HOLDING AS?

John Bjørn Moen is registered as general manager of HAMMER MOEN HOLDING AS.

Where is HAMMER MOEN HOLDING AS based?

HAMMER MOEN HOLDING AS has its business address in Innvik.

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.