BIZTRAC BETA
Rental and operating of own or leased real estate

SONE AS

Org. no. 992035242 Limited company (AS) Rakkestad Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 52,000
Operating profit NOK −76,000
Equity NOK 4.6m
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−76k kr).

SONE AS is registered as a limited company in Rakkestad, Østfold with organisation number 992035242. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av maskiner og annet utstyr, eiendom med mer. Samt kjøp/salg av aksjer og investeringer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 52,000 in revenue and NOK −76,000 in operating profit.

Key figures · 2024

Revenue
NOK 52,000
Operating profit
NOK −76,000
Equity
NOK 4.6m
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns SONE AS?

STEIN OVE NYBORG
SONE AS
NOK 52,000 rev. · NOK −76,000 profit

SONE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SONE AS own?

SONE AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SONE AS

Who owns SONE AS?

STEIN OVE NYBORG is the largest registered owner, with 100.0%.

What is the revenue of SONE AS?

SONE AS had revenue of NOK 52,000 in 2024.

Who is the general manager of SONE AS?

Stein Ove Nyborg is registered as general manager of SONE AS.

Where is SONE AS based?

SONE AS has its business address in Degernes.

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.