BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

SHADY BUSINESS AS

Org. no. 929636007 Limited company (AS) Lillehammer Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 125,000
Operating profit NOK 3,000
Equity NOK 81,000
Incorporated 2022
Share capital NOK 100,000

SHADY BUSINESS AS is registered as a limited company in Lillehammer, Innlandet with organisation number 929636007. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, salg og utleie av utstyr til arrangementer.”. The most recent filed accounts, for the 2025 financial year, show NOK 125,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2025

Revenue
NOK 125,000
Operating profit
NOK 3,000
Equity
NOK 81,000
Est. value
NOK 60,000

Financial health · 2025

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

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

Who owns SHADY BUSINESS AS?

JØRGEN KRISTOFFER SÆTHER
SHADY BUSINESS AS
NOK 125,000 rev. · NOK 3,000 profit

SHADY BUSINESS AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SHADY BUSINESS AS own?

SHADY BUSINESS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SHADY BUSINESS AS

Who owns SHADY BUSINESS AS?

JØRGEN KRISTOFFER SÆTHER is the largest registered owner, with 40.0%.

What is the revenue of SHADY BUSINESS AS?

SHADY BUSINESS AS had revenue of NOK 125,000 in 2025.

Where is SHADY BUSINESS AS based?

SHADY BUSINESS AS has its business address in Lillehammer.

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.