BIZTRAC BETA
Rental and operating of own or leased real estate

SANKING AS

Org. no. 829846772 Limited company (AS) Sandnes Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 754,000
Operating profit NOK 53,000
Equity NOK −149,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−149k kr).
  • Nylig endring 2026-04-08 Adresseendring registrert 2026-04-08.

SANKING AS is registered as a limited company in Sandnes, Rogaland with organisation number 829846772. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 754,000 in revenue and NOK 53,000 in operating profit.

Key figures · 2024

Revenue
NOK 754,000
Operating profit
NOK 53,000
Equity
NOK −149,000
Est. value
NOK 364,000

Financial health · 2024

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.2%
Weak
Equity as a share of total capital

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

Who owns SANKING AS?

MÆHLE HOLDING AS
SANKING AS
NOK 754,000 rev. · NOK 53,000 profit

SANKING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SANKING AS own?

SANKING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SANKING AS

Who owns SANKING AS?

MÆHLE HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of SANKING AS?

SANKING AS had revenue of NOK 754,000 in 2024.

Where is SANKING AS based?

SANKING AS has its business address in Sandnes.

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.