BIZTRAC BETA
Buying and selling of own real estate

NESBRU DETALJ AS

Org. no. 997306457 Limited company (AS) Asker Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 314,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

NESBRU DETALJ AS is registered as a limited company in Asker, Akershus with organisation number 997306457. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i fast eiendom, verdipapirer m.v.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 314,000
Est. value
NOK 286,000

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.5%
Very good
Equity as a share of total capital

Who owns NESBRU DETALJ AS?

CHRISTIAN STEENSTRUP
NESBRU DETALJ AS
NOK 0 rev. · NOK −5,000 profit

NESBRU DETALJ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NESBRU DETALJ AS own?

NESBRU DETALJ AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NESBRU DETALJ AS

Who owns NESBRU DETALJ AS?

CHRISTIAN STEENSTRUP is the largest registered owner, with 100.0%.

What is the revenue of NESBRU DETALJ AS?

NESBRU DETALJ AS had revenue of NOK 0 in 2025.

Who is the general manager of NESBRU DETALJ AS?

Christian Steenstrup is registered as general manager of NESBRU DETALJ AS.

Where is NESBRU DETALJ AS based?

NESBRU DETALJ AS has its business address in Nesbru.

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.