BIZTRAC BETA
Development of building projects

HUSEBYLØKKA AS

Org. no. 995145650 Limited company (AS) Larvik Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK −10,000
Operating profit NOK −55,000
Equity NOK 4.0m
Incorporated 2010
Share capital NOK 100,000

Signals

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

HUSEBYLØKKA AS is registered as a limited company in Larvik, Vestfold with organisation number 995145650. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom og hva herved står i forbindelse med, herunder aksjetegning eller på annen måte gjøre seg interessert i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK −10,000 in revenue and NOK −55,000 in operating profit.

Key figures · 2024

Revenue
NOK −10,000
Operating profit
NOK −55,000
Equity
NOK 4.0m
Est. value
NOK 3.6m

Financial health · 2024

Liquidity
20.88
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
95.2%
Very good
Equity as a share of total capital

Who owns HUSEBYLØKKA AS?

ROLF KRUGE HUSEBY
HUSEBYLØKKA AS
NOK −10,000 rev. · NOK −55,000 profit

HUSEBYLØKKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUSEBYLØKKA AS

Who owns HUSEBYLØKKA AS?

ROLF KRUGE HUSEBY is the largest registered owner, with 100.0%.

What is the revenue of HUSEBYLØKKA AS?

HUSEBYLØKKA AS had revenue of NOK −10,000 in 2024.

Who is the general manager of HUSEBYLØKKA AS?

Rolf Kruge Huseby is registered as general manager of HUSEBYLØKKA AS.

Where is HUSEBYLØKKA AS based?

HUSEBYLØKKA AS has its business address in Tjodalyng.

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.