BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

BIOREG NATUR OG MILJØ AS

Org. no. 930739308 Limited company (AS) Aure Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 714,000
Equity NOK 1.0m
Incorporated 2023
Employees 5
Share capital NOK 30,000

BIOREG NATUR OG MILJØ AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 930739308. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor natur og miljø.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 714,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 714,000
Equity
NOK 1.0m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns BIOREG NATUR OG MILJØ AS?

LANGELO AS
BIOREG NATUR OG MILJØ AS
NOK 3.5m rev. · NOK 714,000 profit

BIOREG NATUR OG MILJØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIOREG NATUR OG MILJØ AS

Who owns BIOREG NATUR OG MILJØ AS?

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

What is the revenue of BIOREG NATUR OG MILJØ AS?

BIOREG NATUR OG MILJØ AS had revenue of NOK 3.5m in 2025.

Who is the general manager of BIOREG NATUR OG MILJØ AS?

Geir Frode Langelo is registered as general manager of BIOREG NATUR OG MILJØ AS.

Where is BIOREG NATUR OG MILJØ AS based?

BIOREG NATUR OG MILJØ AS has its business address in Foldfjorden.

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.