BIZTRAC BETA
Buying and selling of own real estate

HUNGRY HEART AS

Org. no. 925477540 Limited company (AS) Larvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 781,000
Operating profit NOK 10,000
Equity NOK 63,000
Incorporated 2020
Share capital NOK 30,000

HUNGRY HEART AS is registered as a limited company in Larvik, Vestfold with organisation number 925477540. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder investering i fast eiendom, kjøp og salg av aksjer, samt konsulentvirksomhet, forlagsvirksomhet og alt hva derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 781,000 in revenue and NOK 10,000 in operating profit.

Key figures · 2024

Revenue
NOK 781,000
Operating profit
NOK 10,000
Equity
NOK 63,000
Est. value
NOK 70,000

Financial health · 2024

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

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

Who owns HUNGRY HEART AS?

BRUCE ATLE KARLSEN
HUNGRY HEART AS
NOK 781,000 rev. · NOK 10,000 profit

HUNGRY HEART AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HUNGRY HEART AS own?

HUNGRY HEART AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HUNGRY HEART AS

Who owns HUNGRY HEART AS?

BRUCE ATLE KARLSEN is the largest registered owner, with 50.0%.

What is the revenue of HUNGRY HEART AS?

HUNGRY HEART AS had revenue of NOK 781,000 in 2024.

Where is HUNGRY HEART AS based?

HUNGRY HEART 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.