BIZTRAC BETA
Architectural activities

SJO FASTING AS

Org. no. 966811714 Limited company (AS) Sandnes Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 13.3m
Operating profit NOK 2.9m
Equity NOK 1.5m
Incorporated 1993
Employees 10
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SJO FASTING AS is registered as a limited company in Sandnes, Rogaland with organisation number 966811714. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 1993 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Yte tjeneste som arkitekter, firma/ eiendoms- taksering, konsulentbistand innen nevnte fagområde opplæring/ utdanning, eiendoms- og prosjekt- utviklig, eiendomsforvaltning, samt deltakelse i selskaper med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.3m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 13.3m
Operating profit
NOK 2.9m
Equity
NOK 1.5m
Est. value
NOK 11.8m

Financial health · 2024

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.8%
Satisfactory
Equity as a share of total capital

Who owns SJO FASTING AS?

MONEYPENNY AS
SJO FASTING AS
NOK 13.3m rev. · NOK 2.9m profit

SJO FASTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SJO FASTING AS

Who owns SJO FASTING AS?

MONEYPENNY AS is the largest registered owner, with 99.0%.

What is the revenue of SJO FASTING AS?

SJO FASTING AS had revenue of NOK 13.3m in 2024.

Where is SJO FASTING AS based?

SJO FASTING 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.