BIZTRAC BETA
Graphic design and visual communication activities

HAPPY WIFEY AS

Org. no. 913845684 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK −443,000
Equity NOK −367,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−367k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−443k kr).

HAPPY WIFEY AS is registered as a limited company in Asker, Akershus with organisation number 913845684. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utforme grafisk design av tekstilprodukter og kosmetikkprodukter, herunder produksjon og salg av disse produktene samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK −443,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK −443,000
Equity
NOK −367,000

Financial health · 2024

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

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

Who owns HAPPY WIFEY AS?

MIKAEL AS
HAPPY WIFEY AS
NOK 1.6m rev. · NOK −443,000 profit

HAPPY WIFEY AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAPPY WIFEY AS

Who owns HAPPY WIFEY AS?

MIKAEL AS is the largest registered owner, with 47.7%.

What is the revenue of HAPPY WIFEY AS?

HAPPY WIFEY AS had revenue of NOK 1.6m in 2024.

Where is HAPPY WIFEY AS based?

HAPPY WIFEY AS has its business address in Sætre.

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

Report a problem

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