biztrac. BETA
COMPANY REGISTER PROFILE
935095727 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Industrial product and fashion design activities

NETER AS

Org. no. 935095727 Limited company (AS) Kristiansand Incorporated 2025 Active
Revenue 2025 NOK 63,000
Operating profit NOK 17,000
Equity NOK 38,000
Incorporated 2025
Share capital NOK 30,000

NETER AS is registered as a limited company in Kristiansand, Agder with organisation number 935095727. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Levere digitale 3D-modellering og rendering for visualisering av produkter samt teknisk tegning, lysdesign og prototyping som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 63,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 63,000
Operating profit
NOK 17,000
Equity
NOK 38,000
Est. value
NOK 86,000

Financial health · 2025

Liquidity
12.42
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
91.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NETER AS?

NETER AS
NOK 63,000 rev. · NOK 17,000 profit

NETER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NETER AS

Who owns NETER AS?

Eskil Hansen is the largest registered owner, with 100.0%.

What is the revenue of NETER AS?

NETER AS had revenue of NOK 63,000 in 2025.

Where is NETER AS based?

NETER AS has its business address in Kristiansand S.

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.