BIZTRAC BETA
COMPANY REGISTER PROFILE
913252926 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Computer consultancy and computer facilities management activities

SYCIETY AS

Org. no. 913252926 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 644,000
Operating profit NOK 414,000
Equity NOK 1.5m
Incorporated 2014
Share capital NOK 480,000

SYCIETY AS is registered as a limited company in Oslo, Oslo with organisation number 913252926. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2014. Registered share capital is NOK 480,000, divided into 16000 shares. The company's stated purpose is: “Lever IT konsulenttjenester for å fremme effektivisering og økt produktivitet, og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 644,000 in revenue and NOK 414,000 in operating profit.

Key figures · 2025

Revenue
NOK 644,000
Operating profit
NOK 414,000
Equity
NOK 1.5m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns SYCIETY AS?

AASMUND ANDERSEN
SYCIETY AS
NOK 644,000 rev. · NOK 414,000 profit

SYCIETY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYCIETY AS

Who owns SYCIETY AS?

AASMUND ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of SYCIETY AS?

SYCIETY AS had revenue of NOK 644,000 in 2025.

Where is SYCIETY AS based?

SYCIETY AS has its business address in Oslo.

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.