BIZTRAC BETA
COMPANY REGISTER PROFILE
920040810 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

AGNES LAGERBYGG AS

Org. no. 920040810 Limited company (AS) Larvik Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 993,000
Equity NOK 3.3m
Incorporated 2017
Share capital NOK 30,000

AGNES LAGERBYGG AS is registered as a limited company in Larvik, Vestfold with organisation number 920040810. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie av fast eiendom, minilager og containere, deltakelse i andre selskaper, samt hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 993,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 993,000
Equity
NOK 3.3m
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns AGNES LAGERBYGG AS?

AGNES LAGERBYGG AS
NOK 2.1m rev. · NOK 993,000 profit

AGNES LAGERBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGNES LAGERBYGG AS

Who owns AGNES LAGERBYGG AS?

SMARTERE INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of AGNES LAGERBYGG AS?

AGNES LAGERBYGG AS had revenue of NOK 2.1m in 2025.

Who is the general manager of AGNES LAGERBYGG AS?

Cato Johansen is registered as general manager of AGNES LAGERBYGG AS.

Where is AGNES LAGERBYGG AS based?

AGNES LAGERBYGG AS has its business address in Stavern.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.