biztrac. BETA
COMPANY REGISTER PROFILE
986851453 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

BYBROEN AS

Org. no. 986851453 Limited company (AS) Trondheim Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 14.5m
Operating profit NOK −113,000
Equity NOK 3.2m
Incorporated 2004
Employees 17
Share capital NOK 120,000

Signals

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

BYBROEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 986851453. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2004 and has 17 registered employees. Registered share capital is NOK 120,000, divided into 120 shares. The company's stated purpose is: “Restaurant, salg av aromaterapitjenester, utleie av utstyr, eie og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.5m in revenue and NOK −113,000 in operating profit.

Key figures · 2025

Revenue
NOK 14.5m
▲ +5 %
Operating profit
NOK −113,000
▼ −721 %
Equity
NOK 3.2m
▼ −6 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
2.03
Very good
Current assets ÷ current liabilities
Profitability
-1.7%
Not satisfactory
Return on total assets
Solidity
53.8%
Very good
Equity as a share of total capital

Who owns BYBROEN AS?

BYBROEN AS
NOK 14.5m rev. · NOK −113,000 profit

BYBROEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYBROEN AS

Who owns BYBROEN AS?

Carsten Bachke Tourrenc is the largest registered owner, with 100.0%.

What is the revenue of BYBROEN AS?

BYBROEN AS had revenue of NOK 14.5m in 2025.

Who is the general manager of BYBROEN AS?

Carsten Bachke Tourrenc is registered as general manager of BYBROEN AS.

Where is BYBROEN AS based?

BYBROEN AS has its business address in Trondheim.

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.