BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

WAKEUP LIVING AS

Org. no. 995676419 Limited company (AS) Gjøvik Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 20.0m
Operating profit NOK 638,000
Equity NOK 907,000
Incorporated 2010
Share capital NOK 107,000

WAKEUP LIVING AS is registered as a limited company in Gjøvik, Innlandet with organisation number 995676419. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2010. Registered share capital is NOK 107,000, divided into 106750 shares. The company's stated purpose is: “Kjøp og salg av varer og tjenester, eller annen type næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.0m in revenue and NOK 638,000 in operating profit.

Key figures · 2024

Revenue
NOK 20.0m
Operating profit
NOK 638,000
Equity
NOK 907,000
Est. value
NOK 2.4m

Financial health · 2024

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.3%
Satisfactory
Equity as a share of total capital

Who owns WAKEUP LIVING AS?

IDAR STENSVOLD
WAKEUP LIVING AS
NOK 20.0m rev. · NOK 638,000 profit

WAKEUP LIVING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does WAKEUP LIVING AS own?

WAKEUP LIVING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WAKEUP LIVING AS

Who owns WAKEUP LIVING AS?

IDAR STENSVOLD is the largest registered owner, with 84.3%.

What is the revenue of WAKEUP LIVING AS?

WAKEUP LIVING AS had revenue of NOK 20.0m in 2024.

Who is the general manager of WAKEUP LIVING AS?

Idar Stensvold is registered as general manager of WAKEUP LIVING AS.

Where is WAKEUP LIVING AS based?

WAKEUP LIVING AS has its business address in Gjøvik.

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.