BIZTRAC BETA
Repair and maintenance of machinery

NERGÅRD SERVICE AS

Org. no. 928745805 Limited company (AS) Frøya Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 84,000
Operating profit NOK 20,000
Equity NOK 47,000
Incorporated 2022
Share capital NOK 30,000

NERGÅRD SERVICE AS is registered as a limited company in Frøya, Trøndelag with organisation number 928745805. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg og service, reparasjoner og vedlikehold av produkter knyttet til merkantil verksted, samt andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 84,000 in revenue and NOK 20,000 in operating profit.

Key figures · 2025

Revenue
NOK 84,000
Operating profit
NOK 20,000
Equity
NOK 47,000
Est. value
NOK 91,000

Financial health · 2025

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

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

Who owns NERGÅRD SERVICE AS?

STIAN ANDRE NERGÅRD
NERGÅRD SERVICE AS
NOK 84,000 rev. · NOK 20,000 profit

NERGÅRD SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NERGÅRD SERVICE AS

Who owns NERGÅRD SERVICE AS?

STIAN ANDRE NERGÅRD is the largest registered owner, with 100.0%.

What is the revenue of NERGÅRD SERVICE AS?

NERGÅRD SERVICE AS had revenue of NOK 84,000 in 2025.

Who is the general manager of NERGÅRD SERVICE AS?

Stian Andre Nergård is registered as general manager of NERGÅRD SERVICE AS.

Where is NERGÅRD SERVICE AS based?

NERGÅRD SERVICE AS has its business address in Sistranda.

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.