BIZTRAC BETA
Rental and operating of own or leased real estate

BORGEJORDET 80 AS

Org. no. 989026798 Limited company (AS) Larvik Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 1.6m
Equity NOK 3.3m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BORGEJORDET 80 AS is registered as a limited company in Larvik, Vestfold with organisation number 989026798. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og drift av eiendom samt å eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 1.6m
Equity
NOK 3.3m
Est. value
NOK 5.8m

Financial health · 2024

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.9%
Good
Equity as a share of total capital

Who owns BORGEJORDET 80 AS?

HATLO EIENDOM AS
BORGEJORDET 80 AS
NOK 3.1m rev. · NOK 1.6m profit

BORGEJORDET 80 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORGEJORDET 80 AS

Who owns BORGEJORDET 80 AS?

HATLO EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BORGEJORDET 80 AS?

BORGEJORDET 80 AS had revenue of NOK 3.1m in 2024.

Who is the general manager of BORGEJORDET 80 AS?

Lars Kaare Hatlo is registered as general manager of BORGEJORDET 80 AS.

Where is BORGEJORDET 80 AS based?

BORGEJORDET 80 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.