BIZTRAC BETA
Restaurant activities

NYE BRIMI BUE AS

Org. no. 918622977 Limited company (AS) Lom Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 14.7m
Operating profit NOK 833,000
Equity NOK 1.1m
Incorporated 2017
Employees 30
Share capital NOK 1.2m

NYE BRIMI BUE AS is registered as a limited company in Lom, Innlandet with organisation number 918622977. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 30 registered employees. Registered share capital is NOK 1.2m, divided into 125000 shares. The company's stated purpose is: “Hotelldrift, handel, restaurant/kafe, kursing og kulturformidling, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.7m in revenue and NOK 833,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.7m
Operating profit
NOK 833,000
Equity
NOK 1.1m
Est. value
NOK 3.2m

Financial health · 2024

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.7%
Good
Equity as a share of total capital

Who owns NYE BRIMI BUE AS?

TINA BRIMI
NYE BRIMI BUE AS
NOK 14.7m rev. · NOK 833,000 profit

NYE BRIMI BUE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NYE BRIMI BUE AS own?

NYE BRIMI BUE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NYE BRIMI BUE AS

Who owns NYE BRIMI BUE AS?

TINA BRIMI is the largest registered owner, with 50.6%.

What is the revenue of NYE BRIMI BUE AS?

NYE BRIMI BUE AS had revenue of NOK 14.7m in 2024.

Who is the general manager of NYE BRIMI BUE AS?

Dan-Robin Leirvåg is registered as general manager of NYE BRIMI BUE AS.

Where is NYE BRIMI BUE AS based?

NYE BRIMI BUE AS has its business address in Lom.

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.