BIZTRAC BETA
Rental and operating of own or leased real estate

BRYNALII 103 AS

Org. no. 918348107 Limited company (AS) Voss Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 1.9m
Equity NOK 12.5m
Incorporated 2016
Share capital NOK 70,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BRYNALII 103 AS is registered as a limited company in Voss, Vestland with organisation number 918348107. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 70,000, divided into 35000 shares. The company's stated purpose is: “Eige, forvalte og leige ut fast eigedom, samt det som naturleg heng saman med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 1.9m
Equity
NOK 12.5m
Est. value
NOK 13.3m

Financial health · 2024

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

Who owns BRYNALII 103 AS?

GJERALDSTVEIT HOLDING AS
BRYNALII 103 AS
NOK 2.8m rev. · NOK 1.9m profit

BRYNALII 103 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRYNALII 103 AS

Who owns BRYNALII 103 AS?

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

What is the revenue of BRYNALII 103 AS?

BRYNALII 103 AS had revenue of NOK 2.8m in 2024.

Who is the general manager of BRYNALII 103 AS?

Narve Gjeraldstveit is registered as general manager of BRYNALII 103 AS.

Where is BRYNALII 103 AS based?

BRYNALII 103 AS has its business address in Voss.

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.