BIZTRAC BETA
COMPANY REGISTER PROFILE
920445756 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Industrial product and fashion design activities

SMIRMERD AS

Org. no. 920445756 Limited company (AS) Ørland Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 113,000
Incorporated 2018
Share capital NOK 120,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SMIRMERD AS is registered as a limited company in Ørland, Trøndelag with organisation number 920445756. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2018. Registered share capital is NOK 120,000, divided into 120000 shares. The company's stated purpose is: “Utvikle og selge utstyr til havbruksnæringen samt investere i selskap innen havbruksnæringen.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Former names: HYDROMERD AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
▲ +31 %
Equity
NOK 113,000
▼ −6 %
Est. value
NOK 184,000

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
-2.3%
Not satisfactory
Return on total assets
Solidity
39.6%
Good
Equity as a share of total capital

Who owns SMIRMERD AS?

SMIRMERD AS
NOK 0 rev. · NOK −6,000 profit

SMIRMERD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMIRMERD AS

Who owns SMIRMERD AS?

SMIR AS is the largest registered owner, with 100.0%.

What is the revenue of SMIRMERD AS?

SMIRMERD AS had revenue of NOK 0 in 2025.

Where is SMIRMERD AS based?

SMIRMERD AS has its business address in Bjugn.

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

Report a problem

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