BIZTRAC BETA
Buying and selling of own real estate

FURLY LAGERSEKSJONER AS

Org. no. 927019345 Limited company (AS) Larvik Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 317,000
Equity NOK 1.4m
Incorporated 2021
Share capital NOK 30,000

FURLY LAGERSEKSJONER AS is registered as a limited company in Larvik, Vestfold with organisation number 927019345. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom og hva som naturlig hører inn under dette. Selskapet kan eie aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 317,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 317,000
Equity
NOK 1.4m
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns FURLY LAGERSEKSJONER AS?

FURLY AS
FURLY LAGERSEKSJONER AS
NOK 1.5m rev. · NOK 317,000 profit

FURLY LAGERSEKSJONER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FURLY LAGERSEKSJONER AS

Who owns FURLY LAGERSEKSJONER AS?

FURLY AS is the largest registered owner, with 100.0%.

What is the revenue of FURLY LAGERSEKSJONER AS?

FURLY LAGERSEKSJONER AS had revenue of NOK 1.5m in 2024.

Who is the general manager of FURLY LAGERSEKSJONER AS?

Stian Skeie Hessevik is registered as general manager of FURLY LAGERSEKSJONER AS.

Where is FURLY LAGERSEKSJONER AS based?

FURLY LAGERSEKSJONER AS has its business address in Nevlunghavn.

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.