BIZTRAC BETA
Event catering activities

@HOME AS

Org. no. 925432466 Limited company (AS) Ørland Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 228,000
Operating profit NOK −52,000
Equity NOK 6,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−52k kr).

@HOME AS is registered as a limited company in Ørland, Trøndelag with organisation number 925432466. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøpe selge varer og tjenester, produksjon av mat frukt og grønnsaker innen Catering, Take Away, Thaifood salgsvogn grønnsaksbod. og annet som naturlig sammenfaller med dette som transport og utleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 228,000 in revenue and NOK −52,000 in operating profit.

Key figures · 2024

Revenue
NOK 228,000
Operating profit
NOK −52,000
Equity
NOK 6,000
Est. value
NOK 162,000

Financial health · 2024

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

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

Who owns @HOME AS?

ANITSARA HOVDE
@HOME AS
NOK 228,000 rev. · NOK −52,000 profit

@HOME AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about @HOME AS

Who owns @HOME AS?

ANITSARA HOVDE is the largest registered owner, with 80.0%.

What is the revenue of @HOME AS?

@HOME AS had revenue of NOK 228,000 in 2024.

Who is the general manager of @HOME AS?

Anitsara Hovde is registered as general manager of @HOME AS.

Where is @HOME AS based?

@HOME AS has its business address in Brekstad.

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.