BIZTRAC BETA
Buying and selling of own real estate

SAPIENTOR AS

Org. no. 929065751 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 750,000
Operating profit NOK −1.6m
Equity NOK 1.9m
Incorporated 2022
Share capital NOK 96,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,6 mill kr).

SAPIENTOR AS is registered as a limited company in Bærum, Akershus with organisation number 929065751. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 96,000, divided into 321 shares. The company's stated purpose is: “Selskapets formål er å eie, utvikle og leie ut fast eiendom, foreta investeringer i aksjer og gjeldsinstrumenter, deltagelse i andre foretagender, samt tilby rådgivnings- og konsulenttjenester i denne sammenheng.”. The most recent filed accounts, for the 2024 financial year, show NOK 750,000 in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 750,000
Operating profit
NOK −1.6m
Equity
NOK 1.9m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns SAPIENTOR AS?

FIVE REASONS AS
SAPIENTOR AS
NOK 750,000 rev. · NOK −1.6m profit

SAPIENTOR AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SAPIENTOR AS own?

SAPIENTOR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SAPIENTOR AS

Who owns SAPIENTOR AS?

FIVE REASONS AS is the largest registered owner, with 33.3%.

What is the revenue of SAPIENTOR AS?

SAPIENTOR AS had revenue of NOK 750,000 in 2024.

Where is SAPIENTOR AS based?

SAPIENTOR AS has its business address in Lommedalen.

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.