BIZTRAC BETA
Rental and operating of own or leased real estate

AGRI BYGG LEVANGER AS

Org. no. 921310358 Limited company (AS) Surnadal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK 1.9m
Equity NOK 211,000
Incorporated 2018
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.

AGRI BYGG LEVANGER AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 921310358. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK 1.9m
Equity
NOK 211,000
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns AGRI BYGG LEVANGER AS?

AGRI EIENDOMSUTVIKLING AS
AGRI BYGG LEVANGER AS
NOK 3.5m rev. · NOK 1.9m profit

AGRI BYGG LEVANGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGRI BYGG LEVANGER AS

Who owns AGRI BYGG LEVANGER AS?

AGRI EIENDOMSUTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of AGRI BYGG LEVANGER AS?

AGRI BYGG LEVANGER AS had revenue of NOK 3.5m in 2024.

Where is AGRI BYGG LEVANGER AS based?

AGRI BYGG LEVANGER AS has its business address in Surnadal.

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.