BIZTRAC BETA
Architectural activities

EVRYTODDY AS

Org. no. 923564942 Limited company (AS) Larvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 215,000
Operating profit NOK 26,000
Equity NOK 63,000
Incorporated 2019
Share capital NOK 30,000

EVRYTODDY AS is registered as a limited company in Larvik, Vestfold with organisation number 923564942. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor prosjektering av små og mellomstore bygg, samt det som naturlig hører til under dette. Konsulentvirksomhet innenfor IT, samt det som naturlig hører til under dette. Kjøp, salg og utleie av varepartier, samt det som naturlig hører til under dette. Konsert- og arrangementsdrift, samt det som naturlig hører til under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 215,000 in revenue and NOK 26,000 in operating profit.

Key figures · 2024

Revenue
NOK 215,000
Operating profit
NOK 26,000
Equity
NOK 63,000
Est. value
NOK 160,000

Financial health · 2024

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

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

Who owns EVRYTODDY AS?

IAN HOLDING AS
EVRYTODDY AS
NOK 215,000 rev. · NOK 26,000 profit

EVRYTODDY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EVRYTODDY AS

Who owns EVRYTODDY AS?

IAN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of EVRYTODDY AS?

EVRYTODDY AS had revenue of NOK 215,000 in 2024.

Where is EVRYTODDY AS based?

EVRYTODDY AS has its business address in Larvik.

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.