biztrac. BETA
COMPANY REGISTER PROFILE
925145858 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other machinery and equipment

ELEKTRONOMEN AS

Org. no. 925145858 Limited company (AS) Lillesand Incorporated 2020 Active
Operating profit NOK −54,000
Equity NOK −821,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

ELEKTRONOMEN AS is registered as a limited company in Lillesand, Agder with organisation number 925145858. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Former names: HONEY BADGER AS, STYRKE AS, MBL AS

Key figures · 2025

Operating profit
NOK −54,000
▲ +50 %
Equity
NOK −821,000
▼ −190 %

Financial health · 2025

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

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

Who owns ELEKTRONOMEN AS?

ELEKTRONOMEN AS
· NOK −54,000 profit

ELEKTRONOMEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ELEKTRONOMEN AS own?

ELEKTRONOMEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ELEKTRONOMEN AS

Who owns ELEKTRONOMEN AS?

Svend Mauritzen is the largest registered owner, with 100.0%.

Who is the general manager of ELEKTRONOMEN AS?

Svend Mauritzen is registered as general manager of ELEKTRONOMEN AS.

Where is ELEKTRONOMEN AS based?

ELEKTRONOMEN AS has its business address in Brekkestø.

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.