biztrac. BETA
COMPANY REGISTER PROFILE
934385217 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other educational support services n.e.c.

HVERDAGSMORO AS

Org. no. 934385217 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 3,000
Operating profit NOK −18,000
Equity NOK 6,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

HVERDAGSMORO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934385217. The business is classified under other educational support services n.e.c. (NACE 85.699). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av lek- og læringsbaserte produkter rettet mot foreldre, og pedagoger i barnehage og skole.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 3,000
Operating profit
NOK −18,000
▼ −2510 %
Equity
NOK 6,000
▼ −76 %
Est. value
NOK 5,000

Financial health · 2025

Liquidity
20.37
Very good
Current assets ÷ current liabilities
Profitability
-121.6%
Not satisfactory
Return on total assets
Solidity
95.1%
Weak
Equity as a share of total capital

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

Who owns HVERDAGSMORO AS?

HVERDAGSMORO AS
NOK 3,000 rev. · NOK −18,000 profit

HVERDAGSMORO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HVERDAGSMORO AS

Who owns HVERDAGSMORO AS?

M&E INVEST AS is the largest registered owner, with 60.0%.

What is the revenue of HVERDAGSMORO AS?

HVERDAGSMORO AS had revenue of NOK 3,000 in 2025.

Where is HVERDAGSMORO AS based?

HVERDAGSMORO AS has its business address in Heimdal.

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.