biztrac. BETA
COMPANY REGISTER PROFILE
928981975 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

FIELDSTONE AS

Org. no. 928981975 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 20,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

FIELDSTONE AS is registered as a limited company in Oslo, Oslo with organisation number 928981975. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å eie, forvalte og investere i aksjer, verdipapirer, eiendom og andre formuesobjekter, herunder å eie og forvalte selskaper og eierandeler i andre virksomheter, yte konserninterne tjenester samt annen virksomhet som står i naturlig sammenheng med dette.”.

Former names: SCHULZ X AS

Key figures · 2025

Operating profit
NOK −6,000
▼ −22 %
Equity
NOK 20,000
▲ +6 %
Est. value
NOK 22,000

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
5.5%
Weak
Equity as a share of total capital

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

Who owns FIELDSTONE AS?

FIELDSTONE AS
· NOK −6,000 profit

FIELDSTONE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FIELDSTONE AS own?

FIELDSTONE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FIELDSTONE AS

Who owns FIELDSTONE AS?

Nicholas Andreas Schulz is the largest registered owner, with 100.0%.

Where is FIELDSTONE AS based?

FIELDSTONE 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.