biztrac. BETA
COMPANY REGISTER PROFILE
930519456 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Support activities for crop production

NDI AS

Org. no. 930519456 Limited company (AS) Ringerike Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 5.7m
Operating profit NOK 2.5m
Equity NOK 2.0m
Incorporated 2022
Share capital NOK 30,000

NDI AS is registered as a limited company in Ringerike, Buskerud with organisation number 930519456. The business is classified under support activities for crop production (NACE 01.610). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen entreprenørvirksomhet innen jord og skog. Eiendomsdrift og aksjeforvaltning. - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 5.7m
▲ +197 %
Operating profit
NOK 2.5m
▲ +7977 %
Equity
NOK 2.0m
▲ +24370 %
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
4.59
Very good
Current assets ÷ current liabilities
Profitability
160.3%
Very good
Return on total assets
Solidity
78.2%
Very good
Equity as a share of total capital

Who owns NDI AS?

NDI AS
NOK 5.7m rev. · NOK 2.5m profit

NDI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NDI AS

Who owns NDI AS?

Jesper Bernhard Henriksen is the largest registered owner, with 100.0%.

What is the revenue of NDI AS?

NDI AS had revenue of NOK 5.7m in 2025.

Who is the general manager of NDI AS?

Jesper Bernhard Henriksen is registered as general manager of NDI AS.

Where is NDI AS based?

NDI AS has its business address in Nes I Ådal.

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

Report a problem

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