biztrac. BETA
COMPANY REGISTER PROFILE
927963531 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BISON EIENDOM AS

Org. no. 927963531 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 681,000
Equity NOK 14.1m
Incorporated 2021
Share capital NOK 30,000

BISON EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 927963531. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie eiendom, samt kjøp, salg, drift og utleie av eiendom, og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 681,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +270 %
Operating profit
NOK 681,000
▲ +628 %
Equity
NOK 14.1m
▲ +5 %
Est. value
NOK 11.6m

Financial health · 2025

Liquidity
88.80
Very good
Current assets ÷ current liabilities
Profitability
5.4%
Weak
Return on total assets
Solidity
98.6%
Very good
Equity as a share of total capital

Who owns BISON EIENDOM AS?

BISON EIENDOM AS
NOK 1.1m rev. · NOK 681,000 profit

BISON EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BISON EIENDOM AS

Who owns BISON EIENDOM AS?

J S HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BISON EIENDOM AS?

BISON EIENDOM AS had revenue of NOK 1.1m in 2025.

Who is the general manager of BISON EIENDOM AS?

Joachim Selli is registered as general manager of BISON EIENDOM AS.

Where is BISON EIENDOM AS based?

BISON EIENDOM AS has its business address in Klæbu.

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.