BIZTRAC BETA
Site preparation

B&S EIENDOMSUTVIKLING AS

Org. no. 929975944 Limited company (AS) Tana Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 157,000
Operating profit NOK −93,000
Equity NOK 46,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

B&S EIENDOMSUTVIKLING AS is registered as a limited company in Tana, Finnmark with organisation number 929975944. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eiendom og eiendomsutvikling.”. The most recent filed accounts, for the 2024 financial year, show NOK 157,000 in revenue and NOK −93,000 in operating profit.

Key figures · 2024

Revenue
NOK 157,000
Operating profit
NOK −93,000
Equity
NOK 46,000
Est. value
NOK 71,000

Financial health · 2024

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

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

Who owns B&S EIENDOMSUTVIKLING AS?

AS -SRS
B&S EIENDOMSUTVIKLING AS
NOK 157,000 rev. · NOK −93,000 profit

B&S EIENDOMSUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about B&S EIENDOMSUTVIKLING AS

Who owns B&S EIENDOMSUTVIKLING AS?

AS -SRS is the largest registered owner, with 50.0%.

What is the revenue of B&S EIENDOMSUTVIKLING AS?

B&S EIENDOMSUTVIKLING AS had revenue of NOK 157,000 in 2024.

Who is the general manager of B&S EIENDOMSUTVIKLING AS?

Brage Pedersen Kleven is registered as general manager of B&S EIENDOMSUTVIKLING AS.

Where is B&S EIENDOMSUTVIKLING AS based?

B&S EIENDOMSUTVIKLING AS has its business address in Tana.

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.