biztrac. BETA
COMPANY REGISTER PROFILE
953863979 ORG. NO. 2019 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Non-specialised retail sale of predominately food, beverages or tobacco

STEINBUA KARLE STRAND EFTF Bodil Strand Holvik

Org. no. 953863979 Sole proprietorship (ENK) Grong Active
Ownership graph ↗
Revenue 2019 NOK 86,000
Operating profit NOK 3,000
Equity NOK 186,000

STEINBUA KARLE STRAND EFTF Bodil Strand Holvik is registered as a sole proprietorship in Grong, Trøndelag with organisation number 953863979. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The most recent filed accounts, for the 2019 financial year, show NOK 86,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2019

Revenue
NOK 86,000
▼ −3 %
Operating profit
NOK 3,000
▼ −60 %
Equity
NOK 186,000
Est. value
NOK 109,000

Financial health · 2019

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

Who owns STEINBUA KARLE STRAND EFTF Bodil Strand Holvik?

No shareholders are registered for STEINBUA KARLE STRAND EFTF Bodil Strand Holvik in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STEINBUA KARLE STRAND EFTF Bodil Strand Holvik

What is the revenue of STEINBUA KARLE STRAND EFTF Bodil Strand Holvik?

STEINBUA KARLE STRAND EFTF Bodil Strand Holvik had revenue of NOK 86,000 in 2019.

Who is the general manager of STEINBUA KARLE STRAND EFTF Bodil Strand Holvik?

Bodil Nancy Strand Holvik is registered as general manager of STEINBUA KARLE STRAND EFTF Bodil Strand Holvik.

Where is STEINBUA KARLE STRAND EFTF Bodil Strand Holvik based?

STEINBUA KARLE STRAND EFTF Bodil Strand Holvik has its business address in Grong.

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.