BIZTRAC BETA
Preventive health care activities

AT EASE AS

Org. no. 932830469 Limited company (AS) Sandefjord Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 335,000
Operating profit NOK −178,000
Equity NOK −148,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

AT EASE AS is registered as a limited company in Sandefjord, Vestfold with organisation number 932830469. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Forebygge og begrense sykefravær. Fremme folkehelse og livsmestring.”. The most recent filed accounts, for the 2024 financial year, show NOK 335,000 in revenue and NOK −178,000 in operating profit.

Key figures · 2024

Revenue
NOK 335,000
Operating profit
NOK −178,000
Equity
NOK −148,000

Financial health · 2024

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

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

Who owns AT EASE AS?

Inger Johanne Ihle Rasmussen
AT EASE AS
NOK 335,000 rev. · NOK −178,000 profit

AT EASE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AT EASE AS

Who owns AT EASE AS?

Inger Johanne Ihle Rasmussen is the largest registered owner, with 100.0%.

What is the revenue of AT EASE AS?

AT EASE AS had revenue of NOK 335,000 in 2024.

Who is the general manager of AT EASE AS?

Inger Johanne Ihle Rasmussen is registered as general manager of AT EASE AS.

Where is AT EASE AS based?

AT EASE AS has its business address in Stokke.

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.