BIZTRAC BETA
Rental and operating of own or leased real estate

LERSBRYGGA 14-16 AS

Org. no. 989131087 Limited company (AS) Holmestrand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 638,000
Equity NOK 2.5m
Incorporated 2005
Share capital NOK 100,000

LERSBRYGGA 14-16 AS is registered as a limited company in Holmestrand, Vestfold with organisation number 989131087. 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: “Eie og drifte eiendommen(e) Lersbrygga 14 og 16, men også investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 638,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 638,000
Equity
NOK 2.5m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns LERSBRYGGA 14-16 AS?

BJØRN VIGGO GREGERSEN
LERSBRYGGA 14-16 AS
NOK 1.4m rev. · NOK 638,000 profit

LERSBRYGGA 14-16 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LERSBRYGGA 14-16 AS

Who owns LERSBRYGGA 14-16 AS?

BJØRN VIGGO GREGERSEN is the largest registered owner, with 75.0%.

What is the revenue of LERSBRYGGA 14-16 AS?

LERSBRYGGA 14-16 AS had revenue of NOK 1.4m in 2025.

Who is the general manager of LERSBRYGGA 14-16 AS?

Vidar Espegard is registered as general manager of LERSBRYGGA 14-16 AS.

Where is LERSBRYGGA 14-16 AS based?

LERSBRYGGA 14-16 AS has its business address in Sande I Vestfold.

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.