BIZTRAC BETA
Rental and operating of own or leased real estate

BINSPIRED SOLUTIONS AS

Org. no. 925389447 Limited company (AS) Halden Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −4
Equity NOK 13,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4 kr).

BINSPIRED SOLUTIONS AS is registered as a limited company in Halden, Østfold with organisation number 925389447. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eiendomsutvikling, kjøp salg og utleie, samt oppusning, vedlikehold og annet som naturlig faller sammen med dette. Samt investering i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −4
Equity
NOK 13,000
Est. value
NOK 9,000

Financial health · 2024

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

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

Who owns BINSPIRED SOLUTIONS AS?

NIKKO SEGERSTEEN
BINSPIRED SOLUTIONS AS
· NOK −4 profit

BINSPIRED SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BINSPIRED SOLUTIONS AS own?

BINSPIRED SOLUTIONS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BINSPIRED SOLUTIONS AS

Who owns BINSPIRED SOLUTIONS AS?

NIKKO SEGERSTEEN is the largest registered owner, with 100.0%.

Who is the general manager of BINSPIRED SOLUTIONS AS?

Nikko Segersteen is registered as general manager of BINSPIRED SOLUTIONS AS.

Where is BINSPIRED SOLUTIONS AS based?

BINSPIRED SOLUTIONS AS has its business address in Halden.

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.