BIZTRAC BETA
Beverage serving activities

BYGG 121 AS

Org. no. 917556865 Limited company (AS) Horten Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 34,000
Equity NOK −53,000
Incorporated 2016
Employees 26
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−53k kr).

BYGG 121 AS is registered as a limited company in Horten, Vestfold with organisation number 917556865. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2016 and has 26 registered employees. Registered share capital is NOK 30,000, divided into 150 shares. The company's stated purpose is: “Drift av utested/bar med alkoholservering, arrangering av konserter og annen aktivitet som naturlig er tilknyttet dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 34,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 34,000
Equity
NOK −53,000
Est. value
NOK 252,000

Financial health · 2024

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

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

Who owns BYGG 121 AS?

FREDRIK FAGERLI DAHLE
BYGG 121 AS
NOK 4.6m rev. · NOK 34,000 profit

BYGG 121 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGG 121 AS

Who owns BYGG 121 AS?

FREDRIK FAGERLI DAHLE is the largest registered owner, with 33.3%.

What is the revenue of BYGG 121 AS?

BYGG 121 AS had revenue of NOK 4.6m in 2024.

Who is the general manager of BYGG 121 AS?

Håkon Erlend Ellingsen is registered as general manager of BYGG 121 AS.

Where is BYGG 121 AS based?

BYGG 121 AS has its business address in Horten.

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.