biztrac. BETA
COMPANY REGISTER PROFILE
935079764 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

SØRGJERD AS

Org. no. 935079764 Limited company (AS) Trondheim Incorporated 2025 Active
Revenue 2025 NOK 1.7m
Operating profit NOK −8,000
Equity NOK 14,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

SØRGJERD AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935079764. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Tilby grunnarbeidstjenester, herunder, men ikke begrenset til, graving, drenering, sprengning, planering og andre forberedende arbeider for bygge- og anleggsprosjekter. Tilby vaktmester og gartnertjenester på generell basis.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK −8,000
Equity
NOK 14,000
Est. value
NOK 612,000

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
4.8%
Weak
Equity as a share of total capital

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

Who owns SØRGJERD AS?

SØRGJERD AS
NOK 1.7m rev. · NOK −8,000 profit

SØRGJERD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØRGJERD AS

Who owns SØRGJERD AS?

SØRGJERD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SØRGJERD AS?

SØRGJERD AS had revenue of NOK 1.7m in 2025.

Where is SØRGJERD AS based?

SØRGJERD AS has its business address in Trondheim.

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.